dovecot - Dec 2008 - 1.1.7: quota problem, unable to delete mails when quota exceeded

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

This sometimes ends with:
Dec 15 08:36:43 mbox1 dovecot: IMAP(xxx): Disconnected: Internal error 
occurred. Refer to server log for more information. [2008-12-15 08:36:43] 
bytes=409/896

-- 
Arkadiusz Mi?kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

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.

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.

Also I think Dovecot v1.1 should be able to open the mailbox read-only
even if it can't create the dotlock? Are you using v1.0?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20081215/eb1ebb4d/attachment-0002.bin>

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.
> 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.
> Also I think Dovecot v1.1 should be able to open the mailbox read-only
> even if it can't create the dotlock? Are you using v1.0?
1.1.7 as in subject but read-only won't help in deleting mails that cause 
quota being exceeded 8)

-- 
Arkadiusz Mi?kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/