And the right answer is (I just tried it on a non-production filer) the qtree is copied as a directory. All the underlying files also change their inodes.
Tom
On Thu, 24 Feb 2000, Timothy A. McCarthy wrote:
Well, since the qtree exists at the top level anyway, I would expect the move to be from a client at which point it would be an illegal move across filesystems.
--tmac
tkaczma@gryf.net wrote:
On Tue, 22 Feb 2000, Eyal Traitel wrote:
You've did everything fine from my experience. "mv"-ing the qtree's name does not change its inode, so it doesn't change its internal essence as a qtree.
Speaking of which, I've never tried it, but what would happen if you tried to move a qtree up the directory hierarchy? Would it be converted to a plain ol'e directory, ... ?
Tom
Copying it would change it, "mv"-ing it, as was asked in the original email I responded to would not be allowed.
--tmac
tkaczma@gryf.net wrote:
And the right answer is (I just tried it on a non-production filer) the qtree is copied as a directory. All the underlying files also change their inodes.
Tom
On Thu, 24 Feb 2000, Timothy A. McCarthy wrote:
Well, since the qtree exists at the top level anyway, I would expect the move to be from a client at which point it would be an illegal move across filesystems.
--tmac
tkaczma@gryf.net wrote:
On Tue, 22 Feb 2000, Eyal Traitel wrote:
You've did everything fine from my experience. "mv"-ing the qtree's name does not change its inode, so it doesn't change its internal essence as a qtree.
Speaking of which, I've never tried it, but what would happen if you tried to move a qtree up the directory hierarchy? Would it be converted to a plain ol'e directory, ... ?
Tom
-- ******All New Numbers!!!****** ************* *************
Timothy A. McCarthy --> System Engineer, Eastern Region Network Appliance http://www.netapp.com 240-268-2034 Office \ / Page Me at: 240-268-2001 Fax / 888-971-4468
-
Timothy A. McCarthy -
tkaczma＠gryf.net