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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 23 May 2018 19:52:06 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Reindl Harald <h.reindl@...lounge.net>
Cc:     Jan Kara <jack@...e.cz>, Jaco Kroon <jaco@....co.za>,
        linux-ext4 <linux-ext4@...r.kernel.org>,
        Pieter Kruger <pieter@....co.za>
Subject: Re: corrupt filesystem, superblock/journal - fsck

On Wed, May 23, 2018 at 06:33:39PM +0200, Reindl Harald wrote:
> 
> > 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"

It's counter-intuitive, I admit.  The reason why is because resize2fs
can do many more things; it can shrink file systems as well as grow
them; it can move the inode table around to make room if there aren't
enough reserved group descriptor blocks, etc.

The kernel "online grow" code is much simpler, and so it's less prone
to bugs.

							- Ted