- Quotas trees are not usable because you can't mv files from one
quota tree to another (according to the docs).
The docs are slightly misleading here... sure, you can mv files from one to another, but they get copied, not moved. This should not generally be a problem (it's just like a separate mount point).
Could someone from NetApp provide more detail here? I'm sure you can move from one point to another over NFS, but if you are working from /, you can't do an NFS rename call from one tree to another? What happens when you try to use mv?
What can't you do from a NFS/SMB client point of view?
- You have to create the quota tree first... if you already have a
/home and directories in it, you can't "convert" them into a quota tree. You have to start with a new directory from scratch, crated via the "quota qtree newhome" or something similar.
Ugh. If we get another filer, sure, but doesn't do much good for me now.
What Netapp really needs to do is a default quota report by uid/gid type of command on the filer, to avoid the need to set up quotas to track usage.
Agreed. It looks like I'm stuck using "du" for now.
- Dan