On 09/03/99 10:55:20 you wrote:
Can anybody suggest a way to schlep a hierarchy around that is not O(n) in this annoying way?
A qtree identifier is essentially just a third ID, just like user and group ID, set on each file and inherited from the parent directory. So to change the ID requires essentially a recursive chown-type operation that is always going to be proportional to the amount of data "schlepped".
I suppose one could implement a scheme where the changes were not made right away, and instead upon access each parent was checked back to the root to see if the file has the "wrong" qtree ID for the qtree and if so, correct it and then let you access it, but that would be very slow.
Bruce
On Fri, 3 Sep 1999 sirbruce@ix.netcom.com wrote:
So to change the ID requires essentially a recursive chown-type operation that is always going to be proportional to the amount of data "schlepped".
If it really was as fast as a recursive chwon, that would be great, but the Netapp still issues a copy/unlink instead of a rename when moving files between quota trees. This isn't the fault of the client either, because the same thing happens if I mount the filer's root filesystem on the client (so it thinks it is one filesystem), and do a move from there.
I ought to get off my butt and submit an official request for "rm" and "mv" commands that are local to the filer, where those operations can be optimized using the knowledge the filer has that isn't available to the client.
-
Brian Tao -
sirbruce＠ix.netcom.com