From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs mount/create options (was: XFS status update for August 2010)
Date: Wed, 8 Sep 2010 15:38:53 +0200 [thread overview]
Message-ID: <201009081538.54488@zmi.at> (raw)
In-Reply-To: <20100908105858.GZ705@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 2221 bytes --]
On Mittwoch, 8. September 2010 Dave Chinner wrote:
> > On machines with 32MiB or more 32k is the default, but most
> > machines these days have multi-gigabytes of RAM, so at least for
> > RAM>1GiB that could be made default.
>
> That is definitely not true. XFS is widely used in the embedded NAS
> space, where memory is very limited and might be configured with
> many filesystems. 32k is the default because those sorts of machines
> can't afford to burn 2MB RAM per filesystem just in log buffers.
>
> Also, you can go and search the archives or git history as to why we
> don't tune the logbsize based on physical memory size anymore, too.
OK, then the man page should be updated to reflect this "newer logic".
I've got the information directly from there.
> You're getting the wrong information there. largeio affects the
> output of the optimal IO size reported by stat(2). 'stat -f" does
> a statfs(2) call. Try 'stat /disk/db/<file> --format %o'....
Ah, that's better, thank you :-)
> > And while I am at it: Why does "mount" not provide the su=/sw=
> > options that we can use to create a filesystem? Would make life
> > easier, as it's much easier to read su=64k,sw=7 than
> > sunit=128,swidth=896.
>
> You should never, ever need to use the mount options.
..except when a disk is added to the RAID, or it's RAID level gets
changed. Then sw=7 becomes sw=8 or so - or better said: would become, as
then you must use the (I call it strange, error prone) semantics of
sunit/swidth.
> > When I defined su/sw on mkfs, is it enough, or would I always have
> > to specify sunit/swidth with every mount too?
>
> Yes, no. mkfs.xfs stores sunit/swidth on disk in the superblock.
So when I add a disk, I must only once mount with the new sunit/swidth,
and that is stored? That's nice.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-08 13:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:59 XFS status update for August 2010 Christoph Hellwig
2010-09-02 14:59 ` Christoph Hellwig
2010-09-05 7:44 ` Willy Tarreau
2010-09-05 7:44 ` Willy Tarreau
2010-09-05 9:37 ` Michael Monnerie
2010-09-05 10:47 ` Willy Tarreau
2010-09-05 13:08 ` Dave Chinner
2010-09-05 18:56 ` Willy Tarreau
2010-09-05 23:36 ` Dave Chinner
2010-09-06 5:19 ` Willy Tarreau
2010-09-06 5:49 ` xfs mount/create options (was: XFS status update for August 2010) Michael Monnerie
2010-09-08 5:38 ` Michael Monnerie
2010-09-08 10:58 ` Dave Chinner
2010-09-08 13:38 ` Michael Monnerie [this message]
2010-09-08 14:51 ` Dave Chinner
2010-09-08 15:24 ` Emmanuel Florac
2010-09-08 23:34 ` Michael Monnerie
2010-09-08 23:30 ` Michael Monnerie
2010-09-09 7:27 ` Dave Chinner
2010-09-09 8:29 ` Michael Monnerie
2010-09-06 3:22 ` XFS status update for August 2010 Eric Sandeen
2010-09-06 5:10 ` Michael Monnerie
-- strict thread matches above, loose matches on Subject: below --
2010-09-06 22:55 xfs mount/create options (was: XFS status update for August 2010) Richard Scobie
2010-09-06 23:31 ` Michael Monnerie
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=201009081538.54488@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.