linux-ext4 - found an error that e2fsck does not fix

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]

Date:	Fri, 27 Nov 2015 20:11:34 +0100 (CET)
From:	Bo Branten <bosse@....umu.se>
To:	linux-ext4@...r.kernel.org
Subject: found an error that e2fsck does not fix


Hello,

I am debugging an Windows driver for ext4 and when creating an zero length 
file the error below shows up on Linux, while this ofcause is an bug in 
the Windows driver (looks like it forgets to flush some metadata) I wanted 
to report here that every time I run fsck on this test volume it will mark 
it as clean again but without fixing the error, so if I mount and unmount 
the filesystem again it is again in need of fsck wich in turn will mark it 
clean witout fixing the problem.

Test case, testa and testb is created from Windows and only testb gets one 
character written to with notepad:

bo@...ntu:~$ cd /mnt2/src
bo@...ntu:/mnt2/src$ ls -l
ls: cannot access testa: Input/output error
total 4
drwxr-xr-x 15 bo bo 1024 Mar 13  1994 linux-1.0
drwxr-xr-x 13 bo bo 1024 Mar  7  1995 linux-1.2.0
drwxr-xr-x 15 bo bo 1024 Jun  9  1996 linux-2.0
-?????????  ? ?  ?     ?            ? testa
-rw-r--r--  1 bo bo    1 Nov 27 18:21 testb
bo@...ntu:/mnt2/src$ dmesg|tail
[ 1657.016023] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 
failed to flush
[ 1773.388021] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 
failed to flush
[ 1774.908022] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 
failed to flush
[ 2254.276023] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 
failed to flush
[ 3064.029061] EXT4-fs (sdb5): mounted filesystem with ordered data mode. 
Opts: (null)
[ 3081.376794] EXT4-fs error (device sdb5): ext4_ext_check_inode:464: 
inode #3641: comm ls: bad header/extent: invalid magic - magic 0, entries 
0, max 0(0), depth 0(0)
[ 4097.233826] EXT4-fs (sdb5): mounted filesystem with ordered data mode. 
Opts: (null)
[ 4108.835169] EXT4-fs error (device sdb5): ext4_ext_check_inode:464: 
inode #3641: comm ls: bad header/extent: invalid magic - magic 0, entries 
0, max 0(0), depth 0(0)
[ 6333.410987] EXT4-fs (sdb5): mounted filesystem with ordered data mode. 
Opts: (null)
[ 6338.997450] EXT4-fs error (device sdb5): ext4_ext_check_inode:464: 
inode #3641: comm ls: bad header/extent: invalid magic - magic 0, entries 
0, max 0(0), depth 0(0)
bo@...ntu:/mnt2/src$

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