Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 223869 - mv(1) command produces wrong error message
Summary: mv(1) command produces wrong error message
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
Blocks: FC6Update
TreeView+ depends on / blocked
Reported: 2007-01-22 20:28 UTC by Tamal Kanti Nath
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 5.97-12.5.fc6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-19 08:25:28 UTC

Attachments (Terms of Use)

Description Tamal Kanti Nath 2007-01-22 20:28:23 UTC
Description of problem:
The mv(1) command produces a wrong error message.

Version-Release number of selected component (if applicable):

How reproducible:
When I attempt to replace a non-empty directory with another directory, this
wrong error message occurs.

Steps to Reproduce:
1. mkdir -p a/b b
2. date > a/b/c.txt
3. mv b a

Actual results:
mv: cannot move `b' to a subdirectory of itself, `a/b'

Expected results:
mv: directory 'a/b' already exists

Additional info:
Replacement successfully occurs if the destination directory is empty.

Comment 1 Jim Meyering 2007-01-22 20:40:16 UTC
FWIW, upstream (coreutils-6.7) gets this right now: It prints this:
mv: cannot move `b' to `a/b': Directory not empty

Tim, I don't see off-hand where I made that fix.  Let me know if you'd like details.

Comment 2 Tim Waugh 2007-01-23 10:22:17 UTC
If we do another coreutils update for FC6 it would be nice to get this fix in.

Comment 3 Jim Meyering 2007-01-23 20:06:59 UTC
The fix was on the trunk, between 5.92 and 6.0.  Looks safe.;a=commitdiff;h=36a288e41a6

Here's the log entry:

    * src/copy.c (copy_internal): Don't work around old NFS clients like
    SunOS-4.1.4 and Irix 5.3 that set errno to values like EIO and
    ENOTEMPTY upon failed rename.  Otherwise, we risk misinterpreting
    a banal failure as a recursive move-into-self failure.
    Reported by Florent Bayle in <>.

Comment 4 Fedora Update System 2007-04-18 22:37:19 UTC
Fixed in update: coreutils-5.97-12.5.fc6

Note You need to log in before you can comment on or make changes to this bug.