Re: bug in fsck or ext2/ext3?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Antoine Martin <antoine@...>
Cc: <tytso@...>, Linux Kernel Development <linux-kernel@...>
Date: Monday, September 24, 2007 - 1:04 pm

On Mon, Sep 24, 2007 at 05:56:39PM +0100, Antoine Martin wrote:

 > I've got this snapshot of an ext3 filesystem with a directory that
 > simply cannot be removed! (image below is just 1.2MB)
 > As root:
 > # wget http://users.nagafix.co.uk/~antoine/root-broken.bz2
 > # bunzip2 root-broken.bz2
 > # mount -o loop -t ext2 root-broken ./tmp
 > # rm -fr tmp/chroot.broken
 > rm: cannot remove directory (...)
 > Same result when trying to do anything to those files chown/chmod/touch:
 > "Operation not permitted"
 > 
 > Tested with e2fsprogs v1.39 on 3 systems.
 > Not sure where else to post this...

Various files in the directories it complains about have their 'i'
bit set.  lsattr will show you.   chattr -i those files, and the
directory is removable again.

	Dave

-- 
http://www.codemonkey.org.uk
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
bug in fsck or ext2/ext3?, Antoine Martin, (Mon Sep 24, 12:56 pm)
Re: bug in fsck or ext2/ext3?, Alistair John Strachan, (Mon Sep 24, 1:14 pm)
Re: bug in fsck or ext2/ext3?, Dave Jones, (Mon Sep 24, 1:04 pm)
Re: bug in fsck or ext2/ext3?, David Newall, (Mon Sep 24, 2:16 pm)
Re: bug in fsck or ext2/ext3?, Dave Jones, (Mon Sep 24, 2:21 pm)