From: Andrew Dunn <andrew.g.dunn.dod@gmail.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Updating RAID[56] support
Date: Tue, 4 May 2010 10:55:20 -0400 [thread overview]
Message-ID: <j2wbfcaab951005040755h1542ad66x757e426b058e0466@mail.gmail.com> (raw)
In-Reply-To: <28824133.321.1272655413702.JavaMail.root@zimbra>
I am very interested in support for this functionality. I have been
using mdadm for all of my redundant file systems, but it requires I
have homogeneous partitions/drives for a volume. I would very much
like to use a heterogeneous drive structure for a large redundant
volume and have been waiting in anticipation for btrfs to come forth
with this functionality.
On Fri, Apr 30, 2010 at 3:23 PM, Roy Sigurd Karlsbakk <roy@karlsbakk.ne=
t> wrote:
> ----- "David Woodhouse" <dwmw2@infradead.org> skrev:
>
>> I've been looking again at the RAID5/RAID6 support, and updated the
>> tree
>> at git://git.infradead.org/users/dwmw2/btrfs-raid56.git#merged
>>
>> At the moment, we limit writes to a single disk's worth at a time,
>> which
>> means we _always_ do the read-calculateparity-write cycle and suffer
>> the
>> traditional RAID 'write hole' problem.
>
> Out of curiosity, will Btrfs allow for variable block sizes such as w=
ith ZFS?
>
> roy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.ht=
ml
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-05-04 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 18:06 Updating RAID[56] support David Woodhouse
2010-04-30 18:39 ` Josef Bacik
2010-04-30 20:00 ` David Woodhouse
2010-04-30 19:23 ` Roy Sigurd Karlsbakk
2010-05-04 14:55 ` Andrew Dunn [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=j2wbfcaab951005040755h1542ad66x757e426b058e0466@mail.gmail.com \
--to=andrew.g.dunn.dod@gmail.com \
--cc=chris.mason@oracle.com \
--cc=dwmw2@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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).