From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Can't write much data on a degraded mirror
Date: Sat, 10 Mar 2012 19:24:27 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.03.10.19.24.27@cox.net> (raw)
In-Reply-To: 4F5B9B0C.3010504@gmail.com
Andreas Philipp posted on Sat, 10 Mar 2012 19:18:52 +0100 as excerpted:
> Is there any way to willingly write more data to a degraded array? There
> are other use cases for such a possibility as well. Just think of
> migrating from software raid (and lvm) based setup.
It's probably a bug in the current code. Given that btrfs is
experimental, only fit for test data at this time, that's not
surprising. I'd expect it to work properly by the time the experimental
label comes off, and probably some time before that, just not now, at
least in the cases you two are hitting.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2012-03-10 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 19:17 Can't write much data on a degraded mirror Lutz Euler
2012-03-10 18:18 ` Andreas Philipp
2012-03-10 19:24 ` Duncan [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=pan.2012.03.10.19.24.27@cox.net \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).