linux-ext4 - [Bug 200371] 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-prev] [day] [month] [year] [list]

Message-ID: <bug-200371-13602-eBVHiKwd9C@https.bugzilla.kernel.org/>
Date:   Tue, 03 Jul 2018 18:33:23 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200371] Unable to Mount… EXT4: First Meta block group too large

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

--- Comment #3 from mcolgin@...il.com ---
@theodore 

RE:
So I'm really interested in how the file system got to that state.  If you have
the history of how the file system was resized up until now, that would be
really useful.

I went through my "~/.bash_history" to pull out the commands used that lead to
the error. The commands listed under "HISTORY" were performed throughout 2017
and the LV was grown incrementally over time with relative sizing.

HISTORY
=======
lvextend --size +200G /dev/vg_areca/lv_mylvname
resize2fs -f /dev/vg_areca/lv_mylvname
lvextend --size +100G /dev/vg_areca/lv_mylvname
resize2fs /dev/vg_areca/lv_mylvname
lvextend --size +100G /dev/vg_areca/lv_mylvname
resize2fs -f /dev/vg_areca/lv_mylvname
lvextend --size +500G /dev/vg_areca/lv_mylvname
lvextend --size +500G /dev/vg_areca/lv_mylvname
resize2fs -f /dev/vg_areca/lv_mylvname

These "HISTORY" commands are many months old, the command which led to the
error is here.. in which this LV was locked down to a specific size, as no
other files were going to be added to it.. NOTE: the "tune2fs" which reduced
free blocks, my retrieving of "--getbsz" to get an absolutely blocks needed for
the subsequent "lvreduce --size 8766G"

OP THAT LEAD TO ERROR
=====================
e2fsck -f /dev/vg_areca/lv_mylvname
tune2fs -m 0.0 /dev/vg_areca/lv_mylvname
blockdev --getbsz /dev/vg_areca/lv_mylvname
resize2fs /dev/vg_areca/lv_mylvname 8766G
lvreduce --size 8766G /dev/vg_areca/lv_mylvname 
mount /dev/vg_areca/lv_mylvname

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