Topic: Quotas not enabled on fresh install

[lloydh]

My server is a home server and had 2 x 500GB disks in Raid 1, I needed a lot more disk space so I replaced the old disks with 4 x 2TB disks and then did a fresh install using the following.

Code: [Select]

sme raid=5 spares=0 multipart
After the installation I had the following volumes.

Code: [Select]

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/main-root
                      3.9G  1.6G  2.2G  42% /
/dev/mapper/main-tmp  3.9G  137M  3.6G   4% /tmp
/dev/mapper/main-files
                      7.8G  147M  7.3G   2% /home/e-smith/files
/dev/mapper/main-var  3.9G  708M  3.0G  19% /var
/dev/md1               99M   20M   74M  21% /boot
tmpfs                 3.9G     0  3.9G   0% /dev/shm
#
I then used lvextend and resize2fs to extend /dev/mapper/main-files to use the remaining disk space.    I noticed I was getting messages on the screen during boot and shutdown warning Quotas were not working and I now get an email in admin at 12:37am daily containing the following for each user.

Code: [Select]

Cannot query quota for 'user' on '/dev/mapper/main-files': No quota for this user
Obviously Quotas have not been enabled and this is similar to this old bug http://bugs.contribs.org/show_bug.cgi?id=5515 which was closed as not a bug because the user had created custom LV's.

I have never used Quotas and probably will never use them, am I correct in assuming this is happening to me because I used the 'multipart' option for the installation.

My question is, is this a problem and do I need to raise a bug for it.      If I don't need to raise a bug is there any easy way of getting rid of the error messages and emails relating to Quotas.

[CharlieBrady]

I have never used Quotas and probably will never use them, am I correct in assuming this is happening to me because I used the 'multipart' option for the installation.

I believe so. The 'multipart' option was code added long ago by Shad Lords. I don't recall it being done via the bug tracker. Hence it didn't go through the normal review and verification process. I don't recall any changes being made to the quota configuration to make allowance for any variation in partition configuration.