new "mail and ftp user" immediately exceeds its quota

Submitted by christefano on Thu, 11/12/2009 - 14:47 Pro Licensee

Just created a new user to a virtual server in Virtualmin and the user's quota immediately exceeded the default 50MB quota. When deleting the user, I was told in the confirmation that the 1 selected users used only 88 kB of home directory and mail files.

This virtual server has had a half dozen users added to the virtual server already and those were created without a problem. This new problem is reproducible. In my case, I did the following twice and ended up with the same results:

  1. Select virtual server in Virtualmin
  2. Click "Edit Mail and FTP users"
  3. Click "Add a user to this server"
  4. Disable "Primary email address enabled"
  5. Disable "Yes, deliver to mailbox"
  6. Enable "Subversion login enabled"

Checking this new user's home folder, I verified with du -h that it only uses 4 kB. Virtualmin reports that it uses 55.46MB and Usermin utterly dies because the quota has been exceeded.

My workaround was to increase the quota for this user.

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Thu, 11/12/2009 - 19:05

I wonder if perhaps there are files on the system elsewhere with this new user's UID ?

You could check with the following command, run as root :

find / -user username.domain -type f

and see if there are any outside his home directory..

Submitted by christefano on Thu, 11/12/2009 - 19:57 Pro Licensee

Here's the output. It looks like everything is in the user's directory.

Places and names have been changed to protect the innocent.

$ find / -user username.svn -type f
find: `/proc/824/task/824/fd/5': No such file or directory
find: `/proc/824/task/824/fdinfo/5': No such file or directory
find: `/proc/824/fd/5': No such file or directory
find: `/proc/824/fdinfo/5': No such file or directory
/home/whatswhat/domains/domain/homes/username/Maildir/dovecot-uidlist
/home/whatswhat/domains/domain/homes/username/Maildir/dovecot.index
/home/whatswhat/domains/domain/homes/username/Maildir/.sent/dovecot-uidlist
/home/whatswhat/domains/domain/homes/username/Maildir/.sent/dovecot.index
/home/whatswhat/domains/domain/homes/username/Maildir/.sent/dovecot.index.log
/home/whatswhat/domains/domain/homes/username/Maildir/.sent/maildirfolder
/home/whatswhat/domains/domain/homes/username/Maildir/.sent/dovecot.index.cache
/home/whatswhat/domains/domain/homes/username/Maildir/dovecot.index.log
/home/whatswhat/domains/domain/homes/username/Maildir/.drafts/dovecot-uidlist
/home/whatswhat/domains/domain/homes/username/Maildir/.drafts/dovecot.index
/home/whatswhat/domains/domain/homes/username/Maildir/.drafts/dovecot.index.log
/home/whatswhat/domains/domain/homes/username/Maildir/.drafts/maildirfolder
/home/whatswhat/domains/domain/homes/username/Maildir/.drafts/dovecot.index.cache
/home/whatswhat/domains/domain/homes/username/Maildir/dovecot.index.cache
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/attach.pag
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/delreplies.pag
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/dsnreplies.dir
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/delreplies.dir
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/attach.dir
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/inbox.imap
/home/whatswhat/domains/domain/homes/username/.usermin/mailbox/dsnreplies.pag

Submitted by christefano on Thu, 11/12/2009 - 20:10 Pro Licensee

I found the issue. Between the last comment and my original post, I chowned someone's home directory in order to fix what I thought was an unrelated issue. It turns out that several of that user's files (let's call this user "Bob") were owned by the new user ("Alice") that I added today. After further investigation, I learned that someone had tried to delete Bob's account with deluser and then userdel and wasn't able to for some reason.

Submitted by JamieCameron on Thu, 11/12/2009 - 20:17

Ok, that would explain it ..

Submitted by Issues on Sat, 11/28/2009 - 03:20

Automatically closed -- issue fixed for 2 weeks with no activity.