linux-ext4 - journal recovery problems with metadata

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, 8 Aug 2014 15:31:12 -0400
From:	TR Reardon <thomas_reardon@...mail.com>
To:	linux-ext4@...r.kernel.org
Subject: journal recovery problems with metadata_csum, *non-64bit*

Kernel 3.16, e2fsprogs 1.43-WIP (1.42.11 compiled with metadata_csum
support), filesystems mounted with journal_async_commit.

This may be an fsck problem, hard to tell.  I consistently have
problems with journal recovery after hard reboot when filesystem has
metadata_csum.   Interestingly, no problems with 64-bit filesystems.

during journal replay, bogus block numbers are reported.  in this
case, a 128MB file was deleted on two filesystems where the only
difference is 64bit vs non-64bit.  This also happens with or without
bigalloc, though I only document bigalloc case here.

please see attached superblocks, dumped just prior to hard reboot.
disk8=sdm1, disk9=sdn1

dmesg:

[Fri Aug  8 15:16:28 2014] JBD2: Out of memory during recovery.
[Fri Aug  8 15:16:28 2014] JBD2: recovery failed
[Fri Aug  8 15:16:28 2014] EXT4-fs (sdm1): error loading journal
[Fri Aug  8 15:16:27 2014] EXT4-fs (sdn1): recovery complete
[Fri Aug  8 15:16:27 2014] EXT4-fs (sdn1): mounted filesystem with
ordered data mode. Opts: journal_async_commit

fsck:

#e2fsck -f -v /dev/sdm1
e2fsck 1.43-WIP (09-Jul-2014)
disk8: recovering journal
Error writing block 549755813991 (Invalid argument).  Ignore error<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (11332304, counted=11365072).
Fix<y>? yes
Free inodes count wrong (177287, counted=177288).
Fix<y>? yes

disk8: ***** FILE SYSTEM WAS MODIFIED *****

        1656 inodes used (0.93%, out of 178944)
         260 non-contiguous files (15.7%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 1280/363/5
   721201312 blocks used (98.45%, out of 732566384)
           0 bad blocks
         358 large files

        1267 regular files
         380 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
        1647 files

Download attachment "disk8-dumpe2fs-postrm" of type "application/octet-stream" (2068 bytes)

Download attachment "disk9-dumpe2fs-postrm" of type "application/octet-stream" (2077 bytes)