From: Chris Hunter <chris.hunter@yale.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: e2fsck discrepancy with debugfs stat ?
Date: Fri, 11 Sep 2015 08:39:04 -0400 [thread overview]
Message-ID: <55F2CB68.1020507@yale.edu> (raw)
In-Reply-To: <55F2449D.9090000@yale.edu>
To follow-up on my own question,
The "dry-run" e2fsck does not replay the ext journal. So my discrepancy,
e2fsck reports a unused/deleted inode bug debugfs is able to access the
inode & file data, could be due to uncommitted journal transactions.
regards,
chris hunter
chris.hunter@yale.edu
On 09/10/2015 11:03 PM, Chris Hunter wrote:
> Hi,
> Are there scenarios where e2fsck will report a deleted/unused inode but
> debugfs is able to read the inode structure ?
>
> Some details:
> I am using lustre version of e2fsprogs (1.42.12.wc1). When I run e2fsck
> in nofix/dry-run mode on a blockdev, I receive errors about unused inodes.
> eg)
> > $ e2fsck -nfv <DEV>
>> e2fsck 1.42.12.wc1 (15-Sep-2014)
>> Warning: skipping journal recovery because doing a read-only
>> filesystem check.
>> Pass 1: Checking inodes, blocks, and sizes
>> Pass 2: Checking directory structure
>> Entry '131249395' in /O/0/d19 (118843419) has deleted/unused inode
>> 5671802. Clear? no
> etc...
>
> However when I run command debugfs -c -R "stat /O/0/d19/131249395"
> <DEV>, I can retrieve inode contents. Further debugfs "dump" will
> successfully pull the contents (980 bytes) of the file entry.
>
> thanks,
> chris hunter
> chris.hunter@yale.edu
next prev parent reply other threads:[~2015-09-11 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 3:03 e2fsck discrepancy with debugfs stat ? Chris Hunter
2015-09-11 12:39 ` Chris Hunter [this message]
2015-09-11 17:55 ` Theodore Ts'o
2015-09-11 19:59 ` Chris Hunter
2015-09-12 2:09 ` Theodore 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=55F2CB68.1020507@yale.edu \
--to=chris.hunter@yale.edu \
--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.