On Mon, 2008-12-15 at 09:04 +0100, Arkadiusz Miskiewicz wrote: > On Monday 15 of December 2008, Timo Sirainen wrote: > > On Mon, 2008-12-15 at 08:44 +0100, Arkadiusz Miskiewicz wrote: > > > Hi, > > > > > > When user exceeds it's quota then dovecot can't create it's files and > > > it's showing zero mails :( This also means that user is unable to delete > > > it's own mails. Sounds like kind-of bug, right? > > > > > > Dec 15 08:28:37 mbox1 dovecot: IMAP(xxx): > > > open(/var/mail/xxx/dovecot-uidlist.lock) failed: Disk quota exceeded > > > Dec 15 08:28:37 mbox1 dovecot: IMAP(kdudus): > > > file_dotlock_create(/var/mail/xxx/dovecot-uidlist) failed: Disk quota > > > exceeded > > > > I don't think the mbox file should be modified if it's not locked. I > > suppose it's not very ideal either if user can't delete mails then, but > > at least the mailbox doesn't get corrupted. > > I use maildirs only.
Oh, I didn't read the error message closely enough. > > Anyway, you most likely don't really need to use dotlocks at all. Just > > make sure that your MDA uses fcntl locks and set mbox_write_locks=fcntl. > > Will look. Right now I'm trying to move CONTROL to other fs where quota > doesn't apply to see what will happen. Yes, changing the CONTROL to non-quota partition is the only way to solve this for now. I suppose it should be possible to have the existing mails visible though, but mails not listed in dovecot-uidlist can't really be made visible.
signature.asc
Description: This is a digitally signed message part