bin/118367: mv(1) behaves differently when handling with different file systems

Xin LI delphij at FreeBSD.org
Fri Nov 30 17:40:01 PST 2007


>Number:         118367
>Category:       bin
>Synopsis:       mv(1) behaves differently when handling with different file systems
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Dec 01 01:40:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Xin LI
>Release:        FreeBSD 7.0-BETA3 i386
>Organization:
The FreeBSD Project
>Environment:
System: FreeBSD freefall.freebsd.org 7.0-BETA3 FreeBSD 7.0-BETA3 #30: Fri Nov 30 23:12:12 UTC 2007 simon at freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386


>Description:
	mv(1) behaves differently when operating on same file system vs on
different system, which is not desired.  Also it conflicts with the manpage
documented behavior.

>How-To-Repeat:
Test1: Moving within one filesystem:

mkdir -p t/a/b
mkdir -p b/c/d
cd t/
mv ../b a

Resulting tree:
	t/
		a/
			b/
				c/
					d/

However, with different filesystems:

mkdir -p t/a/b
mkdir -p /tmp/b/c/d
cd t
mv /tmp/b a

We get:

	t/
		a/
			b/
				b/
					c/
						d/
>Fix:

	N/A at the moment.  PR sent because dds@ shows some interest.

>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list