----- Original Message ----- From: Muhlestein, Mark mark.muhlestein@netapp.com To: 'Graham C. Knight' grahamk@ast.lmco.com; toasters@mathworks.com Sent: Friday, February 25, 2000 9:52 AM Subject: RE: mv'ing between qtrees
The problem is that every inode in a qtree has a qtree id in it. You'd have to update the contents of the inode, adjusting the id and updating quotas. Of course, that would be faster (in most cases) than actually copying the data for all files. I'm sure there are other issues, such as the fact that any NFS filehandles referring to the old qtree would be stale, but it's an idea that keeps coming up so I've submitted an RFE for this: 22411.
This subject came up on the list before and I thought an RFE or somesuch was submitted then, but I could be wrong. I had the same idea... while a mv is problematic it could be faster than a cp if implemented.
Bruce