From: Andreas Dilger <adilger@sun.com>
To: Kevin Shanahan <kmshanah@ucwb.org.au>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 bug and/or e2fsck hole
Date: Tue, 07 Apr 2009 16:58:35 -0700 [thread overview]
Message-ID: <20090407235835.GI3204@webber.adilger.int> (raw)
In-Reply-To: <20090407233955.GA4328@kulgan>
On Apr 08, 2009 09:09 +0930, Kevin Shanahan wrote:
> hermes:~# debugfs -c -R 'imap 383' /dev/dm-0
> debugfs 1.41.3 (12-Oct-2008)
> /dev/dm-0: catastrophic mode - not reading inode or group bitmaps
> 383: File not found by ext2_lookup
> hermes:~# debugfs -c -R 'imap <383>' /dev/dm-0
> debugfs 1.41.3 (12-Oct-2008)
> /dev/dm-0: catastrophic mode - not reading inode or group bitmaps
> Inode 383 is part of block group 0
> located at block 312, offset 0x0e00
In the meantime you can use "debugfs -w /dev/dm-0", "clri {filename}"
to zero out the inode, "freei {filename}" to mark the inode unused,
and "rm {filename}" to remove the file from the directory.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-04-07 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 20:48 ext4 bug and/or e2fsck hole Kevin Shanahan
2009-04-07 23:13 ` Andreas Dilger
2009-04-07 23:39 ` Kevin Shanahan
2009-04-07 23:51 ` Andreas Dilger
2009-04-07 23:58 ` Andreas Dilger [this message]
2009-04-08 4:43 ` Kevin Shanahan
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=20090407235835.GI3204@webber.adilger.int \
--to=adilger@sun.com \
--cc=kmshanah@ucwb.org.au \
--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 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).