From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Updating RAID[56] support
Date: Fri, 30 Apr 2010 21:23:33 +0200 (CEST) [thread overview]
Message-ID: <28824133.321.1272655413702.JavaMail.root@zimbra> (raw)
In-Reply-To: <1272564366.3367.4143.camel@macbook.infradead.org>
----- "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 with ZFS?
roy
next prev parent reply other threads:[~2010-04-30 19:23 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 [this message]
2010-05-04 14:55 ` Andrew Dunn
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=28824133.321.1272655413702.JavaMail.root@zimbra \
--to=roy@karlsbakk.net \
--cc=chris.mason@oracle.com \
--cc=dwmw2@infradead.org \
--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 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.