Here's something that's puzzled me about NetApps for a long time. I would often like to move entire hierarchies of directories out from under one qtree into another. And I'd like to do it fast.
I can see why this should take a long time if the qtrees were in different volumes, but they're not.
And I can see why this should take a long time if quotas were being enforced, but I do a quota off before the move and a quota on afterwards.
And it still takes forever...a forever, in fact, that is proportional to the quantity of data being relocated, so it looks as if files are being copied on the disk surface. Huh?
Can anybody suggest a way to schlep a hierarchy around that is not O(n) in this annoying way?
(Incidentally, the last time I tried this was on a 5.1.x).
Brian
Moving directories between qtrees does involve a copy. Each qtree is like a separate volume. One reason is that unix qtrees are reported to Windows systems as a FAT file system, whereas NTFS and mixed qtrees are reported as NTFS file systems.
Joan Pearson
At 10:55 AM 9/3/99 , Brian Rice wrote:
Here's something that's puzzled me about NetApps for a long time. I would often like to move entire hierarchies of directories out from under one qtree into another. And I'd like to do it fast.
I can see why this should take a long time if the qtrees were in different volumes, but they're not.
And I can see why this should take a long time if quotas were being enforced, but I do a quota off before the move and a quota on afterwards.
And it still takes forever...a forever, in fact, that is proportional to the quantity of data being relocated, so it looks as if files are being copied on the disk surface. Huh?
Can anybody suggest a way to schlep a hierarchy around that is not O(n) in this annoying way?
(Incidentally, the last time I tried this was on a 5.1.x).
Brian
-
Brian Rice -
Joan Pearson