simon_clawson@mentorg.com (Clawson Simon) writes

After adding a new volume to my filer, with quotas etc, when a user issues the quota -v command on his UNIX machine he gets

{dv40ss5::simonc} [5] % quota -v Disk quotas for simonc (uid 17xxx): Filesystem usage quota limit timeleft files quota limit timeleft {dv40ss5::simonc} [6] %

Prior to the disk additions he would get the full quota report.

Any ideas?

You don't specify what sort of "UNIX machine" was involved, but I'll guess from the "ss5" that it is some version of Solaris and that the quota command involved is /usr/sbin/quota (=/usr/ucb/quota).

"quota -v" can only report on mounted filing systems, so the first question is whether the relevant NFS mounts had actually been done at all, especially if they are being done via the automounter. For each NFS mount point, quota(1m) will make an rquotad RPC to the server, unless the "noquota" mount option was used (not the default). If nothing so far explains the empty report, make sure that there really is a per-uid quota for the user on the volume(s) concerned (use the filer "quota report" command). Bear in mind that a per-uid quota that applies only within a particular qtree won't show up in the rquotad RPC response unless the NFS mount is also inside that qtree (not the whole volume).

We gave up trying to house-train /usr/sbin/quota some years ago, mostly because of the way that it reports every mount point separately even when they are all within the same volume (or qtree), giving the same data tediously many times on multi-user systems. We have our own quota program that uses the rquotad RPC to report on a single filing system: $HOME by default. When Solaris 2.6 came along we had to modify it to stat "/home/cet1/." (rather than just "/home/cet1") in order to make sure the automounter had actually done the NFS mount.

Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.