On Thu, 8 Apr 1999, Luke Mewburn wrote:
An aside; on our main student filer (an F330), we have nearly 6000 users, and 2500 separate quota entries; we generate an individual quota entry per student based on subject enrolment. Works quite well, although the `quota resize' takes over two minutes to complete, and I'm a bit sick of the huge messages file :/
How long does it take you to do "quota" on after you add some student entries? I thought "quota resize" didn't handle new entries (it complains about them for tree based quotas).
Would you be interested in "network" quotas? I suggested to NAC that it would be nice if one could share quota information between filers. We'll have 4 filers serving our users. We don't want to prohibit them from writing into each others' directories because statistically it should come out even on all filers, but we don't want to give them 4 times the quota. Network wide quotas would be very nice. The user can get his 100MB and put it wherever he wants.
I'd also like to see the end of quota resize and quota off quota on in conjuction to modifying the quotas file.
We've had our share of quota bugs (especially the ``quota -v doesn't display anything'' problem), but in general, the NetApp quota system works well.
Our problem is that it displays too much. We automount each user's home directory. Since we want to permit them to write into each others directory we have quotas on the qtree housing users' directories. Unfortunately that file system is mounted once for every user :(((((((((. Running quota -v displays data related to every home directory mounted on the box. Unfortunately, it appears that Sun does not support the automounter ":" path option in Solaris 2.6 which would fix the problem.
We automount each users home directory because we want to have a data location independent pathing, i.e. /home/tkaczma instead of /home/filer2/tkaczma. This prevents a lot of headaches when users' directories are moved for some reason, like due to disaster recovery or some migration.
Tom