From: Theodore Tso <tytso@mit.edu>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: hard lockup, followed by ext4_lookup: deleted inode referenced: 524788
Date: Mon, 28 Sep 2009 16:25:07 -0400 [thread overview]
Message-ID: <20090928202507.GB22733@mit.edu> (raw)
In-Reply-To: <20090928191644.GR12922@hexapodia.org>
On Mon, Sep 28, 2009 at 12:16:44PM -0700, Andy Isaacson wrote:
> After a hard lockup and reboot, my test box (running recent Linus git
> 851b147) came up with:
>
> [ 5.016854] EXT4-fs (sda1): mounted filesystem with ordered data mode
> [ 8.809125] EXT4-fs (sda1): internal journal on sda1:8
> [ 10.165239] EXT4-fs error (device sda1): ext4_lookup: deleted inode referenced: 524788
> [ 10.165286] Aborting journal on device sda1:8.
> [ 10.168111] EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal
> [ 10.168169] EXT4-fs (sda1): Remounting filesystem read-only
> [ 10.171614] EXT4-fs (sda1): Remounting filesystem read-only
It would be useful to see what pathname is associated with inode 524788.
You can use debugfs to find this out. For example to find a pathname
which points to inode 14666, you can do this:
# debugfs /dev/sda1
debugfs 1.41.9 (22-Aug-2009)
debugfs: ncheck 14666
Inode Pathname
14666 /grub/menu.lst
Also try using the debugfs stat command, send me the output, please:
debugfs: stat <14666>
> 2. after a lockup the journal recovery should not fail.
I'm not sure it was a matter of the journal recovery failing. All we
know for certain is that filesystem was corrupted after the lockup and
remounting the filesystem. What caused the file system corruption is
open to question at the moment; it could have been caused by the
lockup; or it could have been a file that was deleted right about the
time of the lockup; or it could have been some completely random
filesystem corruption that.
It would be useful to know whether the inode was in question was
supposed to have been deleted. If it was, it would be useful to know
if the dtime reported by debugfs's stat was around the time of the
original lockup.
- Ted
next prev parent reply other threads:[~2009-09-28 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 19:16 hard lockup, followed by ext4_lookup: deleted inode referenced: 524788 Andy Isaacson
2009-09-28 20:25 ` Theodore Tso [this message]
2009-09-28 21:28 ` Andy Isaacson
2009-09-29 3:13 ` Theodore Tso
2009-09-29 16:12 ` Andy Isaacson
2009-09-30 19:38 ` Andy Isaacson
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=20090928202507.GB22733@mit.edu \
--to=tytso@mit.edu \
--cc=adi@hexapodia.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).