From: Andreas Dilger <adilger@Sun.COM>
To: Iavor Stoev <iavor@icdsoft.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 MAX journal size ?
Date: Mon, 07 Dec 2009 15:16:07 -0700 [thread overview]
Message-ID: <3470552D-0538-4F6E-BEA4-E85C97148E87@sun.com> (raw)
In-Reply-To: <4B1D77B1.8090805@icdsoft.com>
On 2009-12-07, at 14:46, Iavor Stoev wrote:
> I wonder if the Ext3's MAX journal size of 102,400 file system blocks
> has been increased in Ext4.
>
> I'm using 10TB 4k block Ext3 file system with external journal on
> Gigabyte I-Ram drive and I'm planning a migration to Ext4 system.
> And I wonder if I can increase the journal size over 400MB.
Well, even with ext3 the maximum journal size was only for internal
journals. It was always possible to have larger external journal
devices.
With ext4, the maximum journal size WAS increased, though this is in
fact a mke2fs/tune2fs limit so it is also increased for new ext3
filesystems.
Note that with large journals you are also consuming an equal amount
of RAM as the size of the journal, so don't make it crazy big. Having
a journal on SSD is only really noticable for sync-happy workloads.
It isn't noticably better than using a regular disk for the external
journal if you aren't doing a lot of syncs (e.g. NFS or email).
I've thought in the past that it might be an interesting hack to use a
huge journal device (say 32GB) with data journaling, and then have the
JBD layer get the data blocks from the journal for checkpointing to
the filesystem instead of keeping the buffers pinned in RAM. That
would would allow blazing metadata workloads, zero seeking, and then
checkpointing in bulk to the filesystem. ... but unfortunately not
something I have time to test out.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-12-07 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 21:46 Ext4 MAX journal size ? Iavor Stoev
2009-12-07 22:16 ` Andreas Dilger [this message]
2009-12-08 16:43 ` Iavor Stoev
2009-12-08 18:26 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3470552D-0538-4F6E-BEA4-E85C97148E87@sun.com \
--to=adilger@sun.com \
--cc=iavor@icdsoft.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox