On Thu, 9 Dec 1999, Steven W Orr wrote:
> Yesterday someone tried to rename a directory. The result was that the
> content of the directory got copied to the new place
>
> mv a b
>
> caused the content of a to be copied to the new b tree. When I looked to
> see what was going on I noticed that a was a local mount point and that
> both a and b were in the root partition. So on the one hand, a was not
> being moved *to* a new partition, but OTOH, a is a mount point.
>
> Can someone please explain what was going on here?
well, historically, "mv" has never been allowed to move across
filesystems, since all it did was a relink using the same ilist.
clearly, since "a" is a mount point, you're trying to move what
is in one filesystem to another. the linux form of "mv" apparently
has some fallback position where, if it can't do a legitimate move,
it does a recursive copy and deletes the original files.
i'm suspecting that, even though you don't mention it, the "a"
directory is now empty, no?
rday
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
