linux-ext4 - e2fsck discrepancy with debugfs stat ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <55F2449D.9090000@yale.edu>
Date:	Thu, 10 Sep 2015 23:03:57 -0400
From:	Chris Hunter <chris.hunter@...e.edu>
To:	linux-ext4@...r.kernel.org
Subject: e2fsck discrepancy with debugfs stat ?

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@...e.edu
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html