From: Bill Davidsen <davidsen@tmr.com>
To: Iordan Iordanov <iordan@cdf.toronto.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: write barriers on raid0 and raid10
Date: Wed, 16 Jun 2010 11:37:52 -0400 [thread overview]
Message-ID: <4C18EFD0.1030707@tmr.com> (raw)
In-Reply-To: <4C0E8A88.8010906@cdf.toronto.edu>
Iordan Iordanov wrote:
> Hi,
>
> We are designing a rather involved file server with an ext3 formatted
> stripe (raid0) sitting on top of raid10 devices. Each raid10 device
> sits on top of 3 iscsi targets, and has layout n3 (so it is
> effectively a 3 way mirror). We chose raid10 over raid1 due to an
> apparent read performance benefit of raid10.
>
> We are trying to decide whether to upgrade to a kernel newer than
> 2.6.34, where write barriers are ostensibly supported by all possible
> raid types, because we are worried about ext3 corruption with no write
> barrier support.
>
> However, we are also worried about whether write barriers really "make
> sense" in a multi-disk environment and are wondering whether they will
> actually make a difference in our setup. For argument's sake, let's
> assume that our drives honor write cache flushes.
>
> Can somebody shed some light on how write barriers are implemented in
> raid0 and raid10? Also, any critical comments on the validity of our
> setup and/or assumptions is also welcome.
>
I'm sorry not to see an answer here, I'm interested as well.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
next prev parent reply other threads:[~2010-06-16 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1751539Ab0FHSI6/20100608180858Z+3813@vger.kernel.org>
2010-06-08 18:23 ` write barriers on raid0 and raid10 Iordan Iordanov
2010-06-16 15:37 ` Bill Davidsen [this message]
2010-06-16 21:21 ` Neil Brown
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=4C18EFD0.1030707@tmr.com \
--to=davidsen@tmr.com \
--cc=iordan@cdf.toronto.edu \
--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 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.