From: Chen Huan <chenhuan@nrchpc.ac.cn>
To: linux-ext4@vger.kernel.org
Subject: e2fsck aborts when invalid indirect block is encountered
Date: Thu, 1 Sep 2011 14:34:10 +0800 [thread overview]
Message-ID: <20110901063410.GA8313@notebook.chenhuan> (raw)
Hi, All.
During a recent read-only checking of an corrupted ext3 file system,
I found a strange behaviour of e2fsck: when an inode has an invalid
indirect block number, e2fsck aborts with the following message:
e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Inode 12 has illegal block(s). Clear? no
Illegal block #-1 (4294967295) in inode 12. IGNORED.
Error while iterating over blocks in inode 12: Illegal indirect block found
e2fsck: aborted
You can reproduce it with this code snippet:
#!/bin/sh
dev=/dev/sde
mnt=/mnt
mkfs.ext3 -F $dev
mount $dev $mnt
dd if=/dev/zero of=$mnt/file bs=1M count=1
umount $dev
debugfs -w -R 'sif file block[IND] 0xFFFFFFFF' $dev
e2fsck -f -n $dev
Doing a fixing without -n option can safely delete this bad blocknum.
My question is: Is this behaviour a bug or intended?
next reply other threads:[~2011-09-01 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 6:34 Chen Huan [this message]
2011-09-01 8:17 ` e2fsck aborts when invalid indirect block is encountered Andreas Dilger
2011-09-01 8:52 ` Chen Huan
2011-09-01 17:00 ` Ted Ts'o
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=20110901063410.GA8313@notebook.chenhuan \
--to=chenhuan@nrchpc.ac.cn \
--cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.