linux-ext4 - Re: [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers

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:	Tue, 14 Jul 2009 17:26:25 -0400
From:	Andreas Dilger <adilger@....com>
To:	Adrian Hunter <adrian.hunter@...ia.com>
Cc:	Andrew.Morton.akpm@...ux-foundation.org,
	Andreas.Dilger.adilger@....com, Stephen.Tweedie.sct@...hat.com,
	Artem Bityutskiy <artem.bityutskiy@...ia.com>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 2/2] HACK: do I/O read requests while ext3 journal	recovers

On Jul 14, 2009  17:03 +0300, Adrian Hunter wrote:
> The ext3 journal can take a long time to recover at mount
> time.  That was partially fixed by placing a barrier into
> the I/O queue and then not waiting for the actual I/O to
> complete.

Note that you can also reduce the journal recovery time by
reducing the size of the journal.  Having a large journal
is needed for getting good performance with lots of updates
at high speeds.  If you aren't doing a large amount of
filesystem IO (which I'd guess for an embedded device, assuming
you are using it for that), then you could reduce the size of
the journal to the minimum (1000 blocks) and this will also
reduce the recovery time correspondingly.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
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