On Wed, 4 Mar 2015, Sebastian Hagedorn wrote:
Hi,
--On 4. März 2015 11:48:19 +0100 "Giuseppe Ravasio (LU)"
<giuseppe_ravasio@xxxxxxxxxxx> wrote:
We have about 500k growing (that aren't opened daily!) imap folders and
the 0k lock files are filling the inode table of the partition
containing the mboxname_lockpath
the best solution (IMO) is to use shared memory:
mboxname_lockpath: /dev/shm/cyrus_lock
Interesting! I haven't looked at the lock directory until just now. It
uses a lot of inodes on my system too:
/var/spool/cyrus/config/lock# find . | wc -l
444409
It happens to reside on my root partition, and it is using a good chunk of
the available inodes:
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdi2 1189024 628547 560477 53% /
I'm using a tmpfs for the Cyrus {configdir}/proc directory, like so:
tmpfs /var/spool/cyrus/config/proc tmpfs size=25M,nr_inodes=10k 0 0
On my system, /dev/shm has an inode limit as well:
Filesystem Inodes IUsed IFree IUse% Mounted on
tmpfs 1025011 1 1025010 1% /dev/shm
Maybe it would be better to create {configdir}/lock as a separate tmpfs?
Something like:
tmpfs /var/spool/cyrus/config/proc tmpfs size=25M,nr_inodes=10000k 0 0
There is no reason for lock files to persist between Cyrus restarts,
right?
Andy
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
