From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: interesting use case for multiple devices and delayed raid?
Date: Wed, 01 Apr 2009 05:17:27 -0400 [thread overview]
Message-ID: <1238577447.9099.150.camel@pc.interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
I have a use case that I wonder if anyone might find interesting
involving multiple device support and delayed raid.
Let's say I have a system with two disks of equal size (to make it easy)
which has sporadic, heavy, write requirements. At some points in time
there will be multiple files being appended to simultaneously and at
other times, there will be no activity at all.
The write activity is time sensitive, however, so the filesystem must be
able to provide guaranteed (only in a loose sense -- not looking for
real QoS reservation semantics) bandwidths at times. Let's say slightly
(but within the realm of reality) less than the bandwidth of the two
disks combined.
I also want both the metadata and file data mirrored between the two
disks so that I can afford to lose one of the disks and not lose (most
of) my data. It is not a strict requirement that all data be
immediately mirrored however.
So it seems that given these requirements that a filesystem should be
able to keep the disks mirrored in a "loose timeframe" so as to provide
redundancy (for all but the currently writing data) but also be able to
provide the full bandwidth of the two disks, yes?
Is this sort of idea on the btrfs roadmap at all?
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-04-01 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:17 Brian J. Murrell [this message]
2009-04-01 10:13 ` interesting use case for multiple devices and delayed raid? Dmitri Nikulin
2009-04-01 21:04 ` Brian J. Murrell
2009-04-02 5:41 ` Dmitri Nikulin
2009-04-02 11:27 ` Chris Mason
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=1238577447.9099.150.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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