Sorry for the long delay before replying, I've been busy lately.
On Tue, Feb 22, 2005 at 04:31:02PM +0000, Chris Thompson wrote:
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)
On my old existing traditional volumes, the data was in a qtree with a qtree quota set to prevent the qtree from consuming all the space in the volume. After 7.0, these qtree mounts showed the user quota in df instead of the qtree quota as in 6.5 and previous. When I created some flexvols, I did not use a qtree for the whole set of data, and df consistantly shows the volume size and free space. (I just now realized I forgot to test creating a new volume and mounting a qtree. With flexvols, I don't intend to use a qtree to put a cap on the data, so I've been mounting the volume directly.)
2. If there is a qtree quota but no user quota, does df still show the qtree quota as before?
I have not tried this. As above I forgot to try testing with mounting a new qtree.
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?
The user executing df has his/her own quota reported as the df results.
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?
I have not mixed these on our volumes, as my old home directory volume had a qtree with a qtree quota and per-user quotas, but my old research data volume had a qtree with a qtree quota and per-group quotas. If I can get the "new" behavior to poke its head out again, I'll try this.
(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...
Chris Thompson Email: cet1@cam.ac.uk
On a whole, I am pretty happy with 7.0 and this was an opportune time to convert to flexvols since we recently obtained a new 2T disk shelf. I did not want to pass up the chance at using our new disk shelf for conversion, and old volumes were filling up so I had to work quick.
Flexvols are working awesome, my quotas appear to be working fine under the hood, and other than df reporting, the only other gotcha for me has been that I need to perform a quota off/on to refresh quotas until they fix "quota resize" for me. I put my trust in NetApp to provide a release that would serve data without crashing, and it is filling that function, and I accept the small issues I've observed as a burden for choosing to run a .0 release of software.