From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Copying a disk containing a btrfs filesystem
Date: Wed, 16 Apr 2014 13:12:47 +0200 [thread overview]
Message-ID: <2723219.5o4fQymcSy@fuchsia> (raw)
In-Reply-To: <5347C663.4050704@swiftspirit.co.za>
On Friday 11 April 2014 12:39:31 Brendan Hide wrote:
> If you're 100% happy with your old disk's *content*/layout/etc (just
> not happy with the disk's reliability), try an
> overnight/over-weekend ddrescue instead
Thanks again to everyone who replied and especially for suggesting
ddrescue. In the meantime, I've got a suitable new disk and copied the
data to it using ddrescue (it took about 12 hours for 1TB). The disk had
one fault extending over a few successive sectors.
For some reason, I had to repair the first partition, which I use for
swap. The large second with btrfs on it seems fine. I ran btrfs scrub on
it and it found one error:
Apr 16 09:48:27 fuchsia kernel: [ 6792.829186] btrfs: checksum error at
logical 74443923456 on dev /dev/sdb2, sector 145398288, root 1228, inode
59102093, offset 929792, length 4096, links 1 (path:
usr/lib/debug/.build-id/8f/b82df57b7b6fff7033f6abd7de914b82f98160.debug)
That file is part of a "historical" snapshot which I have deleted by now
and thus presumably dealt with the problem.
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
prev parent reply other threads:[~2014-04-16 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 13:21 Copying a disk containing a btrfs filesystem Michael Schuerig
2014-04-10 13:58 ` Duncan
2014-04-10 14:53 ` Michael Schuerig
2014-04-10 14:00 ` George Eleftheriou
2014-04-10 15:15 ` Duncan
2014-04-10 15:51 ` Michael Schuerig
2014-04-10 16:01 ` George Eleftheriou
2014-04-10 16:24 ` Michael Schuerig
2014-04-11 0:35 ` Duncan
2014-04-10 18:15 ` Martin Steigerwald
2014-04-10 17:17 ` Jan Kouba
2014-04-10 18:36 ` Michael Schuerig
2014-04-10 22:25 ` Jan Kouba
2014-04-11 10:39 ` Brendan Hide
2014-04-16 11:12 ` Michael Schuerig [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=2723219.5o4fQymcSy@fuchsia \
--to=michael.lists@schuerig.de \
--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.