Jaye Mathisen mrcpu@cdsnet.net writes:
which is flatly impossible, the users were just created and assigned. yet it thinks the disk space usage is all used up.
We had a similar problem with some 4.2 versions. Basically, files would get created as root and then chowned to a user, but without any quota usage attribution. Later, the user deletes some files. 0 minus some number is a really big number because of integer overflow. Quota exceeded.
It looks like you may have a similar problem.
Generally, quotas are unreliable for us. I always "quota off; quota on" whenever I add a new directory directly under one of our quota trees.
The biggest problem for us is that we don't really want to use quotas to limit disk usage, we just want to track it. It should be really easy to have a "nice quotas" option that causes the filer to never send an EDQUOT (quota exceeded) error. That one feature would make most of our quota problems non-problems.
- Dan
On 15 Jan 1998, Daniel Quinlan wrote:
We had a similar problem with some 4.2 versions. Basically, files would get created as root and then chowned to a user, but without any quota usage attribution.
I don't see that behaviour on our 4.3R3 test box, so Netapp probably fixed it. I can create/copy new files as root and chown them, or chown one user's files to another. The quota counts are always updated properly. I haven't tried this on a 4.2 filer yet.
On Sun, 18 Jan 1998, Brian Tao wrote:
I don't see that behaviour on our 4.3R3 test box, so Netappprobably fixed it. I can create/copy new files as root and chown them, or chown one user's files to another. The quota counts are always updated properly. I haven't tried this on a 4.2 filer yet.
I forgot to mention that this assume existing quotas for those users. If you add a new user, you will have to do the "quota on/off" thing for the Netapp to track them. If you are always adding new users, a workaround is to preload the filer with empty files each owned by a different user. Keep in mind the memory and disk write hit each quota entry takes, so don't overdo it by adding tens of thousands of users ahead of time. :)
I preloaded 9000 user quotas on our test F210 and it hasn't shown any signs of imminient failure. The amount of checkpoint data written to disk has gone up to around 450K, so I probably wouldn't want to put quite that many users on a production F210. Note that the CPU usage on the F210 goes to 100% while you run the "quota report" command, which in this case takes a good 8 or 9 minutes.
-
Brian Tao -
Daniel Quinlan