Adam McDougall mcdouga9@egr.msu.edu writes:
This sunday I upgraded our production FAS940 from 6.5.3 to 7.0 and noticed NFS clients are reporting the user or group quota as the volume size and free space when running df, when 6.5.3 and earlier used to report the qtree quota. I was suprised by this change and so far have been told by NetApp that it is a bug fix, not a bug. Just wanted to send a heads up to the list to let people know, and wondering if anyone else was affected negatively by this. I like part of the idea of the change but was not expecting it at all. Didn't see it in docs. Its interesting but inappropriate for some of our volumes the way we have quotas setup, and it prevents non-admins from seeing if the volume or qtree is nearing full.
This doesn't sound like a "bug fix" to me, but a change of spec! I'm more than a little doubtful whether it's a good one.
A number of questions occur to me:
1. Does df show user quota when there is no qtree involved? (i.e. the user quota applies to the whole volume)
2. If there is a qtree quota but no user quota, does df still show the qtree quota as before?
3. _Which_ user? The one in the authorisation info in the NFS call? (that doesn't seem consistent with client-side caching) The one owning the NFS-mounted directory?
4. Whatever the answer to (3), how do group quotas come into it? If there is both a user and a group quota, which is used?
(Well, some others too, but that's a start!) Hopefully someone actually running ONTAP 7.0 [*] and NFS will be able to answer some of them!
[*] I'm pencilling in Easter for ONTAP 7.0 here, although Adam's posting doesn't make me any happier about jumping in...