linux-ext4 - ENOSPC inline_data fsck failure

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 28 Feb 2020 18:52:34 +0800
From:   Murphy Zhou <jencce.kernel@...il.com>
To:     linux-ext4@...r.kernel.org
Subject: ENOSPC inline_data fsck failure

Hi,

With inline_data mkfs option, generic/083 can easily trigger
a fsck failure like this:

-------------------------
seed = 1583104156
_check_generic_filesystem: filesystem on /dev/loop1 is inconsistent
*** fsck.ext4 output ***
fsck 1.46-WIP (09-Oct-2019)
e2fsck 1.46-WIP (09-Oct-2019)
Pass 1: Checking inodes, blocks, and sizes
Inode 94 extent tree (at level 1) could be shorter.  Optimize? no
...
Pass 2: Checking directory structure
Entry 'c6b' in /p2/d6/d100 (32920) has an incorrect filetype (was 3,
should be 1).
Fix? no
Entry 'ca4' in /pa/d0/d4/d34/d26/dde (75) has an incorrect filetype (was
3, should be 1).
Fix? no
...
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 107 ref count is 2, should be 1.  Fix? no
Unattached inode 119
Connect to /lost+found? no
...
-------------------------

The testcase is doing a simple testing: make a small(256M) fs,
run fsstress in it,  make it out of space. Then fsck.

Not sure about is this an issue of ext4 filesystem or e2fsck
needs more options.

Thanks!

-- 
Murphy