From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: ag selection
Date: Mon, 11 Nov 2013 20:42:40 +0100 [thread overview]
Message-ID: <52813330.1020308@itwm.fraunhofer.de> (raw)
In-Reply-To: <5281223A.7010503@sandeen.net>
Hello Eric,
On 11/11/2013 07:30 PM, Eric Sandeen wrote:
> On 11/11/13, 12:23 PM, Bernd Schubert wrote:
>
>> One of my colleagues benchmarked this on one of our fast systems and another
>> colleague current needs this system for other tests, so I don't have the
>> exact parameters. However, it was for sure formated with options like these:
>>
>> mkfs.xfs -d su=256k,sw=10 -l version=2,su=256k -isize=512 /dev/sdX
>>
>> and mounted with these options:
>>
>> mount -onoatime,nodiratime,largeio,inode64,swalloc,allocsize=131072k,nobarrier /dev/sdX <mountpoint>
>
> With all due respect, this is excessive knob-twiddling. Slow down. ;)
>
> * V2 logs are default already, so -l version=2 is redundant.
Well, some of our customer are using fhgfs + xfs on old systems and we
don't want to create a list
"with kernel/xfsprogs version < xyz, you need knob abc..."
So better add it by default, as long as it does not hurt.
> * noatime implies nodiratime, so specifying both is redundant.
Ok, I didn't add it to our default options, but I also didn't care about
it.
> * "largeio" only changes the st_blksize value reported (from default page size to, in your case, the total stripe width). Does that actually affect your application behavior?
Fhgfs does not care about it, but for some backup tools (I think rsync
does/did? read it) it helps.
>
> Backing up, what kernel & what userspace versions are you testing?
xfsprogs-3.1.1-10.el6 + kernel 3.11.
Cheers,
Bernd
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-11 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:25 ag selection Bernd Schubert
2013-11-11 17:53 ` Carlos Maiolino
2013-11-11 17:55 ` Carlos Maiolino
2013-11-11 18:23 ` Bernd Schubert
2013-11-11 18:30 ` Eric Sandeen
2013-11-11 19:42 ` Bernd Schubert [this message]
2013-11-11 20:55 ` Dave 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=52813330.1020308@itwm.fraunhofer.de \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=sandeen@sandeen.net \
--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