From: Stan Hoeppner <stan@hardwarefreak.com>
To: CoolCold <coolthecold@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: XFS on top RAID10 with odd drives count and 2 near copies
Date: Mon, 13 Feb 2012 20:49:01 -0600 [thread overview]
Message-ID: <4F39CB9D.2050500@hardwarefreak.com> (raw)
In-Reply-To: <CAGqmV7o6SNGV_A=iP2-uJXAJpPwh83GuqTZ-BzuY6vceMJJPVg@mail.gmail.com>
On 2/13/2012 3:40 PM, CoolCold wrote:
> While doing this dirty tests, I've seen found that linear md over 3
> subvolumes doesn't support barriers and XFS states this:
> Feb 13 21:39:41 sigma2 kernel: [22336.925917] Filesystem "md6":
> Disabling barriers, trial barrier write failed
> though this doesn't help on iozone random write tests
When using mdraid and a disk controller without BBWC, write barriers
need to be, must be, enabled and working to guarantee journal
consistency. If barriers are disabled here you're risking the integrity
of the entire filesystem. Whatever is causing barriers to be disabled
needs to be fixed. You should definitely ask about this on the XFS
mailing list. You will want to post your complete mdraid
configuration--the 3 RAID1s and the linear, and your xfs_info output,
and describe the underlying storage hardware--controller(s), disks, etc.
Maybe Neil might have some insight here as well.
>> I would recommend copying 48k of those actual picture files evenly
>> across 12 directories, for 4K files per dir. Then use something like
>> curl-loader with a whole lot of simulated clients to hammer on the
>> files. This allows you to test web server performance and IO
>> performance simultaneously.
>
> Yes, this will be more realistic, of course.
By far. Definitely more pain to setup though. If you can get a
synthetic benchy to batch create the ~50K files randomly across the 12
dirs and then randomly read them out after flushing the caches, that
should be pretty close to real world use as well.
--
Stan
prev parent reply other threads:[~2012-02-14 2:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 15:17 XFS on top RAID10 with odd drives count and 2 near copies CoolCold
2012-02-11 4:05 ` Stan Hoeppner
2012-02-11 14:32 ` David Brown
2012-02-12 20:16 ` CoolCold
2012-02-13 8:50 ` David Brown
2012-02-13 9:46 ` CoolCold
2012-02-13 11:19 ` David Brown
2012-02-13 13:46 ` Stan Hoeppner
2012-02-13 8:54 ` David Brown
2012-02-13 9:49 ` CoolCold
2012-02-13 12:09 ` Stan Hoeppner
2012-02-13 12:42 ` David Brown
2012-02-13 14:46 ` Stan Hoeppner
2012-02-13 21:40 ` CoolCold
2012-02-13 23:02 ` keld
2012-02-14 3:49 ` Stan Hoeppner
2012-02-14 8:58 ` David Brown
2012-02-14 11:38 ` keld
2012-02-14 23:27 ` Stan Hoeppner
2012-02-15 8:30 ` Robin Hill
2012-02-15 13:30 ` Stan Hoeppner
2012-02-15 14:03 ` Robin Hill
2012-02-15 15:40 ` David Brown
2012-02-17 13:16 ` Stan Hoeppner
2012-02-17 14:57 ` David Brown
2012-02-17 19:30 ` Peter Grandi
2012-02-18 13:59 ` David Brown
2012-02-19 14:46 ` Peter Grandi
2012-02-17 19:03 ` Peter Grandi
2012-02-17 22:12 ` Stan Hoeppner
2012-02-18 17:09 ` Peter Grandi
2012-02-15 9:24 ` keld
2012-02-15 12:10 ` David Brown
2012-02-15 13:08 ` keld
2012-02-17 18:44 ` Peter Grandi
2012-02-18 17:39 ` Peter Grandi
2012-02-14 7:31 ` CoolCold
2012-02-14 9:05 ` David Brown
2012-02-14 11:10 ` Stan Hoeppner
2012-02-14 2:49 ` Stan Hoeppner [this message]
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=4F39CB9D.2050500@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=coolthecold@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).