From: Chris Mason <chris.mason@oracle.com>
To: Dmitri Nikulin <dnikulin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: interesting use case for multiple devices and delayed raid?
Date: Thu, 02 Apr 2009 07:27:16 -0400 [thread overview]
Message-ID: <1238671636.27540.8.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3a7f57190904012241y40f7a906x3edd1ad8002c3208@mail.gmail.com>
On Thu, 2009-04-02 at 16:41 +1100, Dmitri Nikulin wrote:
> On Thu, Apr 2, 2009 at 8:04 AM, Brian J. Murrell <brian@interlinx.bc.ca> wrote:
> >> A more complete solution, that requires no software changes, would be
> >> to have 3 or 4 disks. A stripe for really fast reads and writes, and
> >> another disk (or another stripe) to act as a slave to the data being
> >> written to the primary stripe. This seems to do what you want, at a
> >> small price premium.
> >
> > No. That's not really what I am describing at all.
>
> Well you get the bandwidth of 2 disks when reading and writing, and
> still mirrored to a second stripe as time permits. Kind of like
> delayed RAID10.
>
> > I apologize if my original description was unclear. Hopefully it is
> > more so now.
>
> Yes. It'll be up to the actual filesystem devs to weigh in on whether
> it's worth implementing.
>
It's an interesting idea, but I think we've got fast front end devices
higher up on the todo list. That will still support the destaging to
slower disks idea, but will be more flexible overall.
-chris
prev parent reply other threads:[~2009-04-02 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:17 interesting use case for multiple devices and delayed raid? Brian J. Murrell
2009-04-01 10:13 ` Dmitri Nikulin
2009-04-01 21:04 ` Brian J. Murrell
2009-04-02 5:41 ` Dmitri Nikulin
2009-04-02 11:27 ` Chris Mason [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=1238671636.27540.8.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=dnikulin@gmail.com \
--cc=linux-btrfs@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