linux-ext4 - Re: corrupt filesystem, superblock/journal

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b077c019-76d5-adf7-0595-3da5261dc1c1@thelounge.net>
Date:   Wed, 23 May 2018 18:33:39 +0200
From:   Reindl Harald <h.reindl@...lounge.net>
To:     "Theodore Y. Ts'o" <tytso@....edu>, Jan Kara <jack@...e.cz>
Cc:     Jaco Kroon <jaco@....co.za>,
        linux-ext4 <linux-ext4@...r.kernel.org>,
        Pieter Kruger <pieter@....co.za>
Subject: Re: corrupt filesystem, superblock/journal - fsck



Am 23.05.2018 um 18:26 schrieb Theodore Y. Ts'o:
> The other thing I'd add is that if you tried doing an off-line resize
> with 1.43.x (x < 9) that could very easily explain how the file system
> originally got corrupted.  There were quite a large number of off-line
> resize bugs for large file systems in older versions of e2fsprogs.
> 
> So users of large file systems are strongly recommended to use
> e2fsprogs 1.44.2, and if you are increasing the file system, using
> on-line file system growth in general will be safer than off-line
> growth.

horrible given that common sense says "don't do online filesystem
changes when you can avoid them"