From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Steven Haigh <netwiz@crc.id.au>, linux-btrfs@vger.kernel.org
Subject: Re: Trying to rescue my data :(
Date: Fri, 24 Jun 2016 13:40:09 -0400 [thread overview]
Message-ID: <d00790ae-bf8d-ee18-06a9-d0c5f6010129@gmail.com> (raw)
In-Reply-To: <dd7fd123-c3a2-7ad0-bf22-a67a1b1a97d7@crc.id.au>
On 2016-06-24 13:05, Steven Haigh wrote:
> On 25/06/16 02:59, ronnie sahlberg wrote:
> What I have in mind here is that a file seems to get CREATED when I copy
> the file that crashes the system in the target directory. I'm thinking
> if I 'cp -an source/ target/' that it will make this somewhat easier (it
> won't overwrite the zero byte file).
You may want to try with rsync (rsync -vahogSHAXOP should get just about
everything possible out of the filesystem except for some security
attributes (stuff like SELinux context), and will give you nice
information about progress as well). It will keep running in the face
of individual read errors, and will only try each file once. It also
has the advantage of showing you the transfer rate and exactly where in
the directory structure you are, and handles partial copies sanely too
(it's more reliable restarting an rsync transfer than a cp one that got
interrupted part way through).
next prev parent reply other threads:[~2016-06-24 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:52 Trying to rescue my data :( Steven Haigh
2016-06-24 16:26 ` Steven Haigh
2016-06-24 16:59 ` ronnie sahlberg
2016-06-24 17:05 ` Steven Haigh
2016-06-24 17:40 ` Austin S. Hemmelgarn [this message]
2016-06-24 17:43 ` Steven Haigh
2016-06-24 17:50 ` Austin S. Hemmelgarn
2016-06-25 4:19 ` Steven Haigh
2016-06-25 16:25 ` Chris Murphy
2016-06-25 16:39 ` Steven Haigh
2016-06-25 17:14 ` Chris Murphy
2016-06-26 2:30 ` Duncan
2016-06-26 3:13 ` Steven Haigh
2016-09-11 19:48 ` compress=lzo safe to use? (was: Re: Trying to rescue my data :() Martin Steigerwald
2016-09-11 20:06 ` Adam Borowski
2016-09-11 20:27 ` Chris Murphy
2016-09-11 20:49 ` compress=lzo safe to use? Hans van Kranenburg
2016-09-12 4:36 ` Duncan
2016-09-17 9:30 ` Kai Krakow
2016-09-12 1:00 ` Steven Haigh
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=d00790ae-bf8d-ee18-06a9-d0c5f6010129@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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).