From: Benjamin Schindler <bschindler@inf.ethz.ch>
To: Michael Weissenbacher <mw@dermichi.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs performance problem
Date: Wed, 27 Apr 2011 10:09:52 +0200 [thread overview]
Message-ID: <4DB7CF50.7050204@inf.ethz.ch> (raw)
In-Reply-To: <4DB7CC01.8090804@dermichi.com>
Hi
On 04/27/2011 09:55 AM, Michael Weissenbacher wrote:
> schrieb Stan Hoeppner:
>> Benjamin Schindler put forth on 4/26/2011 2:44 PM:
>>> Hi
>> Also, slap yourself in the forehead at least 3 times for running your
>> root filesystem on RAID 0. That's akin to riding a motorcycle, naked,
>> in a blizzard, down a steep, winding, ice covered mountain road with no
>> guard rails and a 3000 ft drop. ;)
>>
> If you are really adventurous and don't care about the data on your root
> fs use the following mount options:
> logbsize=256k,delaylog,nobarrier
>
> Personally i would only enable "nobarrier" on Server-Class hardware with
> Battery Backup and proper UPS. But since you are using RAID-0 i suppose
> you really don't care that much about the data on your root fs.
Or stop using raid-0 all together. The performance gain is more than
offset by the barriers and it seems using xfs on just a single disk
would improve performance a lot more than using raid-0 (with disk
failure risk) + risk of corruption due to disabled barriers... or am I
missing something?
>
> Note that both logbsize and delaylog will only have effect on your root
> fs if added to grub.conf (real_rootflags=) since remounting won't
> activate them. Use "cat /proc/mounts" to see if these options were
> really enabled.
>
> hth,
> Michael
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-27 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:44 xfs performance problem Benjamin Schindler
2011-04-26 22:12 ` Stan Hoeppner
2011-04-26 23:23 ` Benjamin Schindler
2011-04-26 23:59 ` Benjamin Schindler
2011-04-29 15:00 ` Peter Grandi
2011-04-30 20:36 ` Michael Monnerie
2011-05-01 8:49 ` Dave Chinner
2011-05-01 14:38 ` Peter Grandi
2011-05-01 15:08 ` Peter Grandi
2011-05-01 15:32 ` Michael Monnerie
2011-05-01 17:04 ` Peter Grandi
2011-05-02 2:50 ` Dave Chinner
2011-05-02 20:10 ` Emmanuel Florac
2011-05-01 13:33 ` Peter Grandi
2011-05-01 16:32 ` Peter Grandi
2011-04-27 7:55 ` Michael Weissenbacher
2011-04-27 8:09 ` Benjamin Schindler [this message]
2011-04-27 2:35 ` Dave Chinner
2011-04-29 16:27 ` Martin Steigerwald
2011-05-01 8:52 ` Dave Chinner
2011-05-01 16:55 ` Christoph Hellwig
2011-05-01 18:24 ` Markus Trippelsdorf
2011-05-02 10:14 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2011-04-29 16:28 Martin Steigerwald
2011-04-29 19:51 ` Peter Grandi
2011-05-01 16:56 ` Benjamin Schindler
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=4DB7CF50.7050204@inf.ethz.ch \
--to=bschindler@inf.ethz.ch \
--cc=mw@dermichi.com \
--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