public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>, xfs@oss.sgi.com
Subject: Re: mkfs.xfs: cannot (re)set log sunit=0
Date: Tue, 27 Jul 2010 13:28:08 +1000	[thread overview]
Message-ID: <20100727032808.GM7362@dastard> (raw)
In-Reply-To: <20100726101238.GA7725@darkside.kls.lan>

On Mon, Jul 26, 2010 at 12:12:39PM +0200, Mario 'BitKoenig' Holbe wrote:
> Hello,
> 
> I intend to set up a XFS filesystem on a RAID0 (Linux md) with 512k
> Chunk Size. Since I cannot align the log section sunit to 512k, and
> since the filesystem will have not much write activity anyways (in fact,
> it'll be mounted read-only most of the time), I tried not to align the
> log section sunit at all via -l sunit=0, but this does not appear to
> work:

Of course - when you specific a value yourself, it has to be a valid
value and for version 2 logs that minimum value for th lsunit is one
log block.  Given that:

....
> log      =internal log           bsize=4096   blocks=2560, version=2
....
                                   ^^^^^^^^^^
Your log block size is 4k, then:

> Is this a bug or a feature?
> 
> The minimum I was able to limit the log sunit to was -l sunit=8, i.e. 1
> block.

This is the correct minimum you are allowed to specify.

> Is there a difference between sunit=0 and sunit=1 in practice or
> are single log entries aligned to blocks anyways?

sunit=0 is an invalid configuration for a version 2 log. Filesystems
without a data sunit default to a lsunit = 1 log block, so in
practice version 2 logs are always aligned/padded in some way.

> Btw...
> Since the filesystem is mostly read-only, I was also thinking about
> reducing the size of the log section. The planned filesystem will be
> 5.5T or bigger, which results in 2G log section per default. I thought
> about limiting it to 128M or 64M. There will be no concurrent write
> activity on the fs. Together with the zero-alignment, what do you think
> about that?

That'll be fine - the maximum log size until a couple of years ago
was 128MB, and I still do most of my benchmarking with a log that
size....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-07-27  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 10:12 mkfs.xfs: cannot (re)set log sunit=0 Mario 'BitKoenig' Holbe
2010-07-27  3:28 ` Dave Chinner [this message]

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=20100727032808.GM7362@dastard \
    --to=david@fromorbit.com \
    --cc=Mario.Holbe@TU-Ilmenau.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