On 09/05/97 02:55:47 you wrote:
Yeah, I'm not sure what would happen if you mount / and try to do the move from one tree to another. But if you mount them separately it won't make any difference (you probably do that anyway, since you want to confine the quota to just /home and not the whole filer). The mv command just does a copy instead.
What can't you do from a NFS/SMB client point of view?
Again, I'm not sure what would happen with the root share, but between shares it will just copy (and then delete if you actually specified a move).
Yep. I complained bitterly about this years ago when a filer was set up the wrong way without a quota tree. You couldn't fix it after the fact. IMHO this is a big problem, as most admins won't understand quota trees when they first start using the filer, and once they do, it's too late to change.
A "quota convert qtree" command would be great, even if it took hours to accomplish for a large directory structure.
Well, don't take me as definitive... maybe someone else has an idea.
Bruce
On Fri, 5 Sep 1997 sirbruce@ix.netcom.com wrote:
Yeah, I'm not sure what would happen if you mount / and try to do the move from one tree to another.
It is treated as a copy (i.e., the semantics of "virtual" filesystems are preserved).
A "quota convert qtree" command would be great, even if it took hours to accomplish for a large directory structure.
Can't you create the quota tree, and then use something like tar to copy/delete files into the quota tree while preserving the directory structure?