From: Iustin Pop <iusty@k1024.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Jasmin Buchert <jasmin@pacifica.ch>, xfs@oss.sgi.com
Subject: Re: mkfs.xfs questions
Date: Fri, 1 Dec 2006 19:30:34 +0100 [thread overview]
Message-ID: <20061201183034.GA20595@teal.hq.k1024.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612010410530.3735@sheep.housecafe.de>
On Fri, Dec 01, 2006 at 04:23:41AM +0000, Christian Kujau wrote:
> On Wed, 29 Nov 2006, Jasmin Buchert wrote:
> >Is there any real advantage of making the log size 32-64 MB and
>
> From 'man mkfs.xfs':
>
> If the log is contained within the data section and size isn't
> specified, mkfs.xfs will try to select a suitable log
> size depending on the size of the filesystem. The actual
> logsize depends on the filesystem block size and the directory
> block size.
>
> Otherwise, the size suboption is only needed if the log
> section of the filesystem should occupy less space than the size
> of the special file.
>
> So, if you're not limited by very special space restrictions, you won't
> need the "size" option.
I don't understand how you took that conclusion. The explanations refer
to the default log size. I believe the original poster asked about the
performance advantage of *raising* the log size above the default values
for internal logs, and my impression is that metadata-intensive
workloads benefit from increasing the log size (however no hard numbers
are available).
A while back when mkfs.xfs had more conservative default value, bigger log
sizes indeed helped for big filesystems.
Regards,
Iustin
next prev parent reply other threads:[~2006-12-01 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 16:45 mkfs.xfs questions Jasmin Buchert
2006-12-01 4:23 ` Christian Kujau
2006-12-01 18:30 ` Iustin Pop [this message]
2006-12-01 23:59 ` Christian Kujau
2006-12-02 11:15 ` Iustin Pop
2006-12-05 17:46 ` Christian Kujau
2006-12-05 18:44 ` Iustin Pop
2006-12-05 21:26 ` David Chinner
2006-12-05 22:28 ` Christian Kujau
2006-12-06 15:57 ` Christian Kujau
2006-12-07 1:23 ` David Chinner
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=20061201183034.GA20595@teal.hq.k1024.org \
--to=iusty@k1024.org \
--cc=jasmin@pacifica.ch \
--cc=lists@nerdbynature.de \
--cc=xfs@oss.sgi.com \
/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