linux-ext4 - Re: 32TB ext4 fsck times

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

Message-ID: <10808.1240466476@gamaville.dokosmarshall.org>
Date:	Thu, 23 Apr 2009 02:01:16 -0400
From:	Nick Dokos <nicholas.dokos@...com>
To:	Valerie Aurora Henson <vaurora@...hat.com>
cc:	Ric Wheeler <rwheeler@...hat.com>, nicholas.dokos@...com,
	linux-ext4@...r.kernel.org
Subject: Re: 32TB ext4 fsck times 

Valerie Aurora Henson <vaurora@...hat.com> wrote:

> Back to something useful the short term... Was the file system created
> with uninitialized block groups and lazy inode table initialization?
> 

Uninit_bg was on but lazy inode table initialization was off.  I tried
turning lazy_itable_init on but e2fsck gets tons of errors, starting
with group descriptor checksum errors.  Unfortunately, I now get group
descriptor checksum errors even without lazy_itable_init and I 'm not
sure why. So I'm back to debugging mke2fs/e2fsck.

Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html