From: Stan Hoeppner <stan@hardwarefreak.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com
Subject: Re: creating a new 80 TB XFS
Date: Fri, 24 Feb 2012 10:51:45 -0600 [thread overview]
Message-ID: <4F47C021.7010008@hardwarefreak.com> (raw)
In-Reply-To: <201202241720.23581.Martin@lichtvoll.de>
On 2/24/2012 10:20 AM, Martin Steigerwald wrote:
> Am Freitag, 24. Februar 2012 schrieb Richard Ems:
>>>> MOUNT
>>>> On mount I will use the options
>>>>
>>>> mount -o noatime,nobarrier,nofail,logbufs=8,logbsize=256k,inode64
>>>> /dev/sdX1 /mount_point
>>>
>>>
>>>
>>> I think that the logbufs/logbsize option matches the default here.
>>> Use delaylog if applicable. See the xfs FAQ.
>>
>> Yes, if I trust the mount manual page, it states "The default value is
>> 8 buffers for any recent kernel." . I suppose 3.2.6 is "a recent
>> kernel", so this could be avoided, but having it explicitly on the
>> mkfs.xfs line does not hurt, or?
>> And for logbsize: "The default value for any recent kernel is 32768."
>>
>> But then at the end of the manual page for mount it says "December
>> 2004", so how actual is this information? Can the default mount values
>> be shown by running mount with some verbose and dry-run parameters?
>
> Does cat /proc/mounts show them? /proc/mounts is more detailed than mount
> or mount -l.
Vanilla kernel.org 3.2.6:
~$ cat /proc/mounts
/dev/sda7 /samba xfs rw,relatime,attr2,delaylog,noquota 0 0
It doesn't show the default logbufs and logbsize values. I asked about
this specific issue over a year ago, because the documentation is
inconsistent, and you can't get the default values out of a running
system. If you can I don't know how. If someone stated a method, I
can't recall it. :(
I do recall Dave, IIRC, saying something to the effect of 'just use the
defaults, as they are 8 and 256K in recent kernels anyway'. That's not
a direct quote, but my recollection.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-24 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 12:52 creating a new 80 TB XFS Richard Ems
2012-02-24 14:08 ` Emmanuel Florac
2012-02-24 15:43 ` Richard Ems
2012-02-24 16:20 ` Martin Steigerwald
2012-02-24 16:51 ` Stan Hoeppner [this message]
2012-02-25 10:59 ` Martin Steigerwald
2012-02-24 16:58 ` Roger Willcocks
2012-02-25 21:57 ` Peter Grandi
2012-02-26 2:57 ` Stan Hoeppner
2012-02-26 16:08 ` Emmanuel Florac
2012-02-26 16:55 ` Joe Landman
2012-02-24 14:52 ` Peter Grandi
2012-02-24 14:57 ` Michael Weissenbacher
2012-02-24 16:05 ` Richard Ems
2012-02-24 15:17 ` Eric Sandeen
2012-10-01 14:28 ` Richard Ems
2012-10-01 14:36 ` Richard Ems
2012-10-01 14:39 ` Eric Sandeen
2012-10-01 14:45 ` Richard Ems
2012-02-27 11:56 ` Michael Monnerie
2012-02-27 12:20 ` Richard Ems
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=4F47C021.7010008@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Martin@lichtvoll.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 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.