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 76954 - rm fails to remove symbolic links
Summary: rm fails to remove symbolic links
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: fileutils
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-30 02:20 UTC by Steve Bonneville
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-10-30 12:58:59 UTC

Attachments (Terms of Use)

Description Steve Bonneville 2002-10-30 02:20:03 UTC
Description of Problem:

  The rm command will not remove symlinks properly.  Behavior is different
  on ext2 and ext3 filesystems, but broken both places.
    On ext2, symlinks may not be removed at all.
    On ext3, symlinks to directories may not be removed.
  Worked fine in 7.3 with fileutils-4.1-10.

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


Steps to Reproduce:

1. touch testfile; ln -s testfile linkfile
2. touch testdir; ln -s testdir linkdir
3. rm linkfile linkdir

Actual Results:
  rm: cannot remove `linkfile/': Not a directory.
  rm: cannot remove `linkdir/': Not a directory.

Expected Results:
  The symlinks "linkfile" and "linkdir" should be deleted.
  The file "testfile" and directory "testdir" should still exist.

Comment 1 Leonid Mamtchenkov 2002-10-30 12:58:53 UTC
First of all, you probably mistyped mkdir with touch in the second step, since
touch does not create directories, afaik.  Secondly, you try to remove the file
like a directory, i.e. with a slash at the end.  This gives the first error. 
Thirdly, since your linkdir is actually a file and not a directory, you get the
same error as above.

I have tried to reproduce the problem you are describing, and could not.  rm
works fine for me. :)

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