linux-ext4 - [Bug 200371] New: Unable to Mount… EXT4: First Meta block group too large

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: <bug-200371-13602@https.bugzilla.kernel.org/>
Date:   Fri, 29 Jun 2018 18:34:48 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200371] New: Unable to Mount… EXT4: First Meta block group too large

https://bugzilla.kernel.org/show_bug.cgi?id=200371

            Bug ID: 200371
           Summary: Unable to Mount… EXT4: First Meta block group too
                    large
           Product: File System
           Version: 2.5
    Kernel Version: 3.10.0-514.26.2.el7.x86_64
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: mcolgin@...il.com
        Regression: No

ERROR
=====
EXT4-fs (dm-46): first meta block group too large: 1152 (group descriptor block
count 1096)

Environment
===========
I have a filesystem, which is ext4, on a machine with
4.17.2-1.el7.elrepo.x86_64. The logical volume is 8.56 TiB.

This filesystem has been resized many times since it was first created.

e2fsck
======
e2fsck 1.42.9 (28-Dec-2013)
/dev/vg_areca/lv_MYLVNAME: clean, 59060/574488576 files, 2294844696/2297954304
blocks


DESC
====
After the last "resize2fs", I started receiving this error via "dmesg". I was
running kernel 3.10.0-514.26.2.el7.x86_64 and after some googling, found that
the current version of linux corrected a bug that produced this error. However,
after updating the kernel, I am still getting the error.

My thoughts are that my multiple resizes has surfaced an issue, but I'm not
sure how to address it.


LINKS
=====

Previous Fix to Kernel with similar error, but appears to be symptomatic

https://www.novell.com/support/kb/doc.php?id=7018898


Results of "debugfs" output (minus 70k entries for Group 70127: (Blocks
2297921536-2297954303) [INODE_UNINIT, ITABLE_ZEROED]") 

https://pastebin.com/EN1xyBAM

-- 
You are receiving this mail because:
You are watching the assignee of the bug.