[Top] [All Lists]

Re: creating a new 80 TB XFS

To: xfs@xxxxxxxxxxx
Subject: Re: creating a new 80 TB XFS
From: Martin Steigerwald <Martin@xxxxxxxxxxxx>
Date: Fri, 24 Feb 2012 17:20:23 +0100
In-reply-to: <4F47B020.4000202@xxxxxxxxxxxxxxxxx>
References: <4F478818.4050803@xxxxxxxxxxxxxxxxx> <20120224150805.243e4906@xxxxxxxxxxxxxxxxxxxx> <4F47B020.4000202@xxxxxxxxxxxxxxxxx> (sfid-20120224_171032_352286_A09775B9)
User-agent: KMail/1.13.7 (Linux/3.2.0-1-amd64; KDE/4.7.4; x86_64; ; )
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.

Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

<Prev in Thread] Current Thread [Next in Thread>