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  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]
Date:	Thu, 10 Sep 2015 23:03:57 -0400
From:	Chris Hunter <>
Subject: e2fsck discrepancy with debugfs stat ?

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.
 > $ 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

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.

chris hunter
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists