From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: Florian Lindner <mailinglists@xgm.de>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Questions about multi-device behavior
Date: Fri, 2 Aug 2013 16:10:31 +0200 [thread overview]
Message-ID: <20130802141031.GB5284@suse.cz> (raw)
In-Reply-To: <CCB92795-C346-467B-B85F-D5CB5C401B77@colorremedies.com>
On Thu, Jul 18, 2013 at 02:05:31PM -0600, Chris Murphy wrote:
>
> On Jul 18, 2013, at 11:33 AM, David Sterba <dsterba@suse.cz> wrote:
>
> >
> > The missing data blocks return IO error and the valid data can be read.
>
> Sounds like if I have a degraded 'single' volume, I can simply cp or
> rsync everything from that volume to another, and I'll end up with a
> successful copy of the surviving data. True?
True.
prev parent reply other threads:[~2013-08-02 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 21:24 Questions about multi-device behavior Florian Lindner
2013-07-17 21:49 ` Chris Murphy
2013-07-18 2:00 ` Roger Binns
2013-07-18 17:33 ` David Sterba
2013-07-18 20:05 ` Chris Murphy
2013-07-18 21:59 ` Roger Binns
2013-07-18 22:03 ` Hugo Mills
2013-08-02 14:10 ` David Sterba [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=20130802141031.GB5284@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mailinglists@xgm.de \
/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).