From: Eric Sesterhenn <snakebyte@gmx.de>
To: sct@redhat.com, akpm@linux-foundation.org, adilger@sun.com
Cc: linux-ext4@vger.kernel.org
Subject: Mounting corrupted ext3 image results in infinite loop
Date: Fri, 21 Nov 2008 10:32:06 +0100 [thread overview]
Message-ID: <20081121093206.GA2672@alice> (raw)
hi,
mounting an intentionally corrupted ext3 image results in
an infinite loop during the mount.
The compressed image can be found here:
http://www.cccmz.de/~snakebyte/ext3.57.img.bz2
mount ./cfs/ext3.57.img /media/test -t ext3 -o debug,data=journal -o
loop
gives the following dmesg output
[ 159.477815] EXT3-fs error (device loop0): ext3_free_branches: Read
failure, inode=8, block=2147483648
[ 159.488844] Aborting journal on device loop0.
[ 159.492602] Remounting filesystem read-only
[ 159.492987] EXT3-fs error (device loop0): ext3_free_branches: Read
failure, inode=8, block=1048576
[ 159.499747] EXT3-fs error (device loop0): ext3_free_branches: Read
failure, inode=8, block=134217792
[ 159.516484] EXT3-fs error (device loop0) in ext3_reserve_inode_write:
Journal has aborted
[ 159.516757] EXT3-fs error (device loop0) in ext3_reserve_inode_write:
Journal has aborted
[ 159.516972] EXT3-fs error (device loop0) in ext3_orphan_del: Journal
has aborted
[ 181.628434] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.628643] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.628815] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.628999] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.629215] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.629383] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
[ 181.629567] ext3_orphan_cleanup: truncating inode 8 to 1049088 bytes
the ext3_orphan_cleanup message is then repeated forever.
Greetings, Eric
reply other threads:[~2008-11-21 9:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081121093206.GA2672@alice \
--to=snakebyte@gmx.de \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).