On 11 Aug 2020, Michael Fritscher told this: > ext4 is fine. In my experience, it is rock-solid, and also fsck.ext4 is > fairly qick (don't know what Roy is doing that it is so slow - do you > really made a full-fledged ext4 with journal or a old ext2 file system?^^) I note that modern mkext2fs leaves whole block groups uninitialized if it can, and any block groups that end up with no files in again get marked uninitalized once more (as of e2fsprogs 1.43). If an older e2fsprogs than that is in use, or if this is an fs too old to support unintialized block groups, or if the fs simply doesn't have uninit_bg enabled (which requires explicit action at creation time, these days), e2fsprogs will be massively slower than if it can exploit the uninitialized bgs to (basically) skip huge chunks of the fsck work on most of the fs that is known to be empty. Without this optimization, one component of fsck time is linear in the total size of the fs: with it, it's linear in the *allocated* space used on the fs. (There are other passes that scale as number of allocated inodes, number of directories, etc.) -- NULL && (void)
