From: Dave T <davestechshop@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: checksum error in metadata node - best way to move root fs to new drive?
Date: Tue, 9 Aug 2016 23:27:56 -0400 [thread overview]
Message-ID: <CAGdWbB5k_HmN2b4zzrnYN+ExiqeP_9Eu9mVBCHEtgZNKHfTARA@mail.gmail.com> (raw)
btrfs scrub returned with uncorrectable errors. Searching in dmesg
returns the following information:
BTRFS warning (device dm-0): checksum error at logical NNNNN on
/dev/mapper/[crypto] sector: yyyyy metadata node (level 2) in tree 250
it also says:
unable to fixup (regular) error at logical NNNNNN on /dev/mapper/[crypto]
I assume I have a bad block device. Does that seem correct? The
important data is backed up.
However, it would save me a lot of time reinstalling the operating
system and setting up my work environment if I can copy this root
filesystem to another storage device.
Can I do that, considering the errors I have mentioned?? With the
uncorrectable error being in a metadata node, what (if anything) does
that imply about restoring from this drive?
If I can copy this entire root filesystem, what is the best way to do
it? The btrfs restore tool? cp? rsync? Some cloning tool? Other
options?
If I use the btrfs restore tool, should I use options x, m and S? In
particular I wonder exactly what the S option does. If I leave S out,
are all symlinks ignored?
I'm trying to save time and clone this so that I get the operating
system and all my tweaks / configurations back. As I said, the really
important data is separately backed up.
I appreciate all suggestions.
next reply other threads:[~2016-08-10 3:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 3:27 Dave T [this message]
2016-08-10 6:27 ` checksum error in metadata node - best way to move root fs to new drive? Duncan
2016-08-10 19:46 ` Austin S. Hemmelgarn
2016-08-10 21:21 ` Chris Murphy
2016-08-10 22:01 ` Dave T
2016-08-10 22:23 ` Chris Murphy
2016-08-10 22:52 ` Dave T
2016-08-11 14:12 ` Nicholas D Steeves
2016-08-11 14:45 ` Austin S. Hemmelgarn
2016-08-11 19:07 ` Duncan
2016-08-11 20:43 ` Chris Murphy
2016-08-12 3:11 ` Duncan
2016-08-12 3:51 ` Chris Murphy
2016-08-11 20:33 ` Chris Murphy
2016-08-11 7:18 ` Andrei Borzenkov
2016-08-11 4:50 ` Duncan
2016-08-11 5:06 ` Gareth Pye
2016-08-11 8:20 ` Duncan
2016-08-12 17:00 ` Patrik Lundquist
2016-08-10 21:15 ` Chris Murphy
2016-08-10 22:50 ` Dave T
2016-08-11 20:23 Dave T
2016-08-12 4:13 ` Duncan
2016-08-12 8:14 ` Adam Borowski
2016-08-12 12:04 ` Austin S. Hemmelgarn
2016-08-12 15:06 ` Duncan
2016-08-15 11:33 ` Austin S. Hemmelgarn
2016-08-12 17:02 ` Chris Murphy
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=CAGdWbB5k_HmN2b4zzrnYN+ExiqeP_9Eu9mVBCHEtgZNKHfTARA@mail.gmail.com \
--to=davestechshop@gmail.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 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.