I have a few quota trees set up on a 540 with 100GB.
I just created some new users, and the filer (running 4.3R4D1) is reporting that they've used:
user 506 9840 41943040 1292 10485760 user 1001 4294966368 41943040 22 10485760 user@web 1001 4294966408 25600 18 1000 user 1003 4294967260 41943040 1 10485760 user@web 1003 4294967260 25600 0 1000 user 1004 4294967260 41943040 1 10485760 user@web 1004 4294967260 25600 0 1000
which is flatly impossible, the users were just created and assigned. yet it thinks the disk space usage is all used up.
What's even weirder is that I can create directories all day, and no errors, only files cause problems. yet the dirs are owned by user 1001, etc.
If anybody has any ideas, I'd love to hear it, occasionally working quotas is worse than no quotas, since it prevents mail from being deliverd (using qmail), yet seems to run OK.
My quota file is trivial, just a few entries.
CC'd to support@netapp, because I have a separate open ticket where df will show -8kb used, -8kb free at odd times.
Any tips appreciated, I could almost strangle this thing.
I have a few quota trees set up on a 540 with 100GB.
I just created some new users, and the filer (running 4.3R4D1) is reporting that they've used:
user 506 9840 41943040 1292 10485760 user 1001 4294966368 41943040 22 10485760 user@web 1001 4294966408 25600 18 1000 user 1003 4294967260 41943040 1 10485760 user@web 1003 4294967260 25600 0 1000 user 1004 4294967260 41943040 1 10485760 user@web 1004 4294967260 25600 0 1000
which is flatly impossible, the users were just created and assigned. yet it thinks the disk space usage is all used up.
Are default quotas being used here? If that's the case, this is likely to be the bug with operations running as root that others in the list have pointed out.
Default quotas trigger the creation of quotas when a user first uses an inode or a data block (by creating a file, for example). This should happen even when the file is created as root and then "chown"ed to the user. This currently fails to happen.
Here is the description from the bug report which should soon get added to the bugs online list on NOW.
TITLE: Derived quotas do not get created for operations running as root, causing usage decrepancies.
DESCRIPTION: Default quotas can cause quotas (derived quotas) to be created on the fly, in response to the first blocks or inodes whose ownership (user or group) requires the creation of derived quotas. This fails to happen for operations that are run as root. For example, a quota will not be created if a file is created as root and then its ownership changed to a user with no quota. Further writes to the file by root will also fail to create the derived quota.
Subsequent operations by the user, such as creation of a file, will trigger the creation of the derived quota, but the usage information in the quota will not include usage prior to creation of the quota.
This may also cause the usage to become negative when data or files are deleted subsequently. The usage appears a large positive number (unsigned representation of the negative number) and is treated as such.
WORKAROUND: Turn quotas off and back on to fix usage discrepancies.
What's even weirder is that I can create directories all day, and no errors, only files cause problems. yet the dirs are owned by user 1001, etc.
This must be because the filer (incorrectly) thinks the user has exceeded the the disk space limit (4294966368 > 41943040), while the number of used files is still within the limit (22 < 10485760). Creation of directories only adds to the used files count, whereas writing to files adds to disk space usage. Turning quotas off and on again should fix this.
-
Jaye Mathisen -
rajeshs＠netapp.com