linux-ext4 - [Bug 194567] ext4 no longer mounts

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 15 Feb 2017 23:46:59 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 194567] ext4 no longer mounts

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

--- Comment #5 from Theodore Tso (tytso@....edu) ---
The meta_bg feature allows file system resizing when (a) there is no
resize_inode, OR (b) when the file system has more than 2**32 blocks.   We
don't enable the meta_bg field and turn off resize_inode by default because for
smaller file systems on HDD's, using the meta_bg slows down the mount by a
little (since the block group descriptors get spread out across the disk).   So
in general the strategy is to use the resize_inode until the file system grows
beyond 2**32 blocks, and only then to switch on the meta_bg feature.   So I was
a bit surprised to see your smallish file system with meta_bg.   This is
supported primarily for debugging / development processes (so we can easily
test meta_bg without needing huge test disks), and not something I had
necessarily had intended for use in production.

(But thanks for being a guinea pig so we could find this bug!  :-)  :-)  :-)

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