On 12/23/2011 11:08 AM, hydra wrote:
Selinux wasn't running.
I can reproduce the problem with this setup:
- restore the maildir with the broken index.cache
- run `/usr/bin/doveadm -D expunge -A mailbox Trash savedbefore 1w` in an
infinite loop
- use horde webmail to access the mail with
Yes, it is reproducible.
About the file, I have tarred up the original maildir before I deleted the
dovecot.index.cache, so when I try to bring in the original file, a 'cat'
does no harm. Moreover, I've tried to do this will all files on the virtual
machine, same results - no harm.
On Thu, Dec
On 12/23/2011 4:12 AM, hydra wrote:
Yes, it is reproducible.
About the file, I have tarred up the original maildir before I deleted the
dovecot.index.cache, so when I try to bring in the original file, a 'cat'
does no harm. Moreover, I've tried to do this will all files on the virtual
Selinux wasn't running.
I can reproduce the problem with this setup:
- restore the maildir with the broken index.cache
- run `/usr/bin/doveadm -D expunge -A mailbox Trash savedbefore 1w` in an
infinite loop
- use horde webmail to access the mail with IMAP
- randomly display messages
I could
Hello Timo, thank you for the reply. I was suspecting the same. However:
- the machine runs under Vmware,
- I've tried 3 different kernel versions,
- I've tried 3 different SCSI controllers.
All same results.
On Wed, Dec 21, 2011 at 6:16 PM, Timo Sirainen t...@iki.fi wrote:
On 21.12.2011, at
On 12/22/2011 8:08 AM, hydra wrote:
Hello Timo, thank you for the reply. I was suspecting the same. However:
- the machine runs under Vmware,
- I've tried 3 different kernel versions,
- I've tried 3 different SCSI controllers.
All same results.
dmesg output? Log errors?
Is your EXT4
On Thu, Dec 22, 2011 at 3:49 PM, Stan Hoeppner s...@hardwarefreak.comwrote:
On 12/22/2011 8:08 AM, hydra wrote:
Hello Timo, thank you for the reply. I was suspecting the same. However:
- the machine runs under Vmware,
- I've tried 3 different kernel versions,
- I've tried 3 different
On 22.12.2011, at 18.06, hydra wrote:
After the virtual machine reboot, the CPU usage is normal again, but just
until doveadm is launched again (it was run from cron). Sorry for the
partition/drive terminology mess up.
So it's reproducible? You could see if you can reproduce it by simply
I suspect, that dovecot v2.0.16 under Linux (tested on Gentoo 3.0.4
Hardened, Gentoo 3.0.6, Gentoo 3.1.4) causes 100% cpu utilization when
index.cache is broken and doveadm is lanched. Dovecot uses LDAP as the
userdb and provides IMAP and LDA. Because each user has a quota, the
doveadm's expunge
On 21.12.2011, at 18.38, hydra wrote:
I suspect, that dovecot v2.0.16 under Linux (tested on Gentoo 3.0.4
Hardened, Gentoo 3.0.6, Gentoo 3.1.4) causes 100% cpu utilization when
index.cache is broken and doveadm is lanched. Dovecot uses LDAP as the
userdb and provides IMAP and LDA. Because
10 matches
Mail list logo
