[Dovecot] Segfault with soft disk quota
RHEL 5.1, dovecot 1.0.rc15 on a x86 system. dovecot -n says
[root@dg mail]# dovecot -n # /etc/dovecot.conf protocols: pop3 pop3s login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login login_process_size: 64 first_valid_uid: 100 mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd
I had one user whose Outlook kept giving disconnection problems. I looked at the logs, and found this:
Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): open(/home/bfarner/Mail/.imap/INBOX/.temp.dg.denmantire.com.4668.564b08eac94 4fe4a) failed: Disk quota exceeded Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): Fixed index file /home/bfarner/Mail/.imap/INBOX/dovecot.index: log file sync pos 2,115528 -> 3, 24 Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): Fixed index file /home/bfarner/Mail/.imap/INBOX/dovecot.index: messages_count 3 -> 0 Mar 31 14:05:31 dg.denmantire.com dovecot: pop3-login: Login: user=<bfarner>, method=PLAIN, rip=192.168.0.37, lip=192.168.0.2 Mar 31 14:05:31 dg.denmantire.com pop3[4668]: segfault at 0000000000000000 rip 00000000004452e8 rsp 00007fff56ccd460 error 4 Mar 31 14:05:31 dg.denmantire.com dovecot: child 4668 (pop3) killed with signal 11
Strange thing is - he's over disk quota, but just over the soft quota - nowhere close to the hard quota.
Easy for me to fix, but I figured I'd also submit it as a bug. I don't follow the list so if you need any more info, please copy my email on the reply. Thanks...
-- Tim Boyer Chief Technology Officer Denman Tire Corporation
On Mon, 2008-03-31 at 14:30 -0400, Tim Boyer wrote:
RHEL 5.1, dovecot 1.0.rc15 on a x86 system. dovecot -n says .. Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): open(/home/bfarner/Mail/.imap/INBOX/.temp.dg.denmantire.com.4668.564b08eac94 4fe4a) failed: Disk quota exceeded
File creation failed with EDQUOT. I fixed a lot of these just before the v1.0.0 release.
Strange thing is - he's over disk quota, but just over the soft quota - nowhere close to the hard quota.
Kernel decided that he was over quota, for whatever reason and failed the syscall. (I don't know how exactly the soft/hard quota rules work)
participants (2)
-
Tim Boyer
-
Timo Sirainen