From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Questions about multi-device behavior
Date: Thu, 18 Jul 2013 14:59:58 -0700 [thread overview]
Message-ID: <ks9ogo$8rg$1@ger.gmane.org> (raw)
In-Reply-To: <CCB92795-C346-467B-B85F-D5CB5C401B77@colorremedies.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18/07/13 13:05, Chris Murphy wrote:
> 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?
Not quite. I did it with cp -a. Because all the metadata survived, cp
would create the target file, but then get an i/o error on opening/reading
the source file. It would print an error message, but not delete the
empty target file. Consequently I ended up with loads of zero length files
I had to go in and delete afterwards.
I briefly looked for an rsync option to keep going on source i/o errors
but didn't find one.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlHoZV4ACgkQmOOfHg372QRPFwCgob01TavS2qffBkxkuv0g9bl3
pC8An25Mgx+cRXb0Kds+GRnzaj2P0Acy
=UA5J
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-18 22:00 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 [this message]
2013-07-18 22:03 ` Hugo Mills
2013-08-02 14:10 ` David Sterba
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='ks9ogo$8rg$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--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).