From: Antoine Martin <antoine@nagafix.co.uk>
To: tytso@thunk.org, Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: bug in fsck or ext2/ext3?
Date: Mon, 24 Sep 2007 17:56:39 +0100 [thread overview]
Message-ID: <46F7EC47.9010803@nagafix.co.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Ted / LKML,
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...
Cheers
Antoine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG9+xHGK2zHPGK1rsRCn6/AJ0S9/D1LTTxsi69uVovKRURa1fFhACfcEzx
8I6nOimUYCFKh9oX6ebnLc0=
=FhTL
-----END PGP SIGNATURE-----
next reply other threads:[~2007-09-24 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 16:56 Antoine Martin [this message]
2007-09-24 17:04 ` bug in fsck or ext2/ext3? Dave Jones
2007-09-24 18:16 ` David Newall
2007-09-24 18:21 ` Dave Jones
2007-09-24 17:14 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46F7EC47.9010803@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@thunk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox