From: Robert Krig <robert.krig@render-wahnsinn.de>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: BTRFS Raid5 error during Scrub.
Date: Sun, 29 Sep 2019 23:38:55 +0200 [thread overview]
Message-ID: <804e7e93a00dfe954222e4f8dc820a075d9ccb79.camel@render-wahnsinn.de> (raw)
Hi guys. First off, I've got backups so no worries there. I'm just
trying to understand what's happening and which files are affected.
I've got a scrub running and the kernel dmesg buffer spit out the
following:
BTRFS warning (device sda): checksum/header error at logical
48781340082176 on dev /dev/sdb, physical 5651115966464: metadata leaf
(level 0) in tree 7
BTRFS warning (device sda): checksum/header error at logical
48781340082176 on dev /dev/sdb, physical 5651115966464: metadata leaf
(level 0) in tree 7
BTRFS error (device sda): bdev /dev/sdb errs: wr 0, rd 0, flush 0,
corrupt 0, gen 1
BTRFS error (device sda): unable to fixup (regular) error at logical
48781340082176 on dev /dev/sdb
BTRFS warning (device sda): checksum/header error at logical
48781340082176 on dev /dev/sdc, physical 5651115966464: metadata leaf
(level 0) in tree 7
BTRFS warning (device sda): checksum/header error at logical
48781340082176 on dev /dev/sdc, physical 5651115966464: metadata leaf
(level 0) in tree 7
BTRFS error (device sda): bdev /dev/sdc errs: wr 0, rd 0, flush 0,
corrupt 0, gen 1
BTRFS error (device sda): unable to fixup (regular) error at logical
48781340082176 on dev /dev/sdc
Is there any way I can find out which files are affected so that I can
just restore them from a backup?
I'm running Debian Buster with Kernel 5.2.
Btrfs-progs v4.20.1
Let me know if you need any further info.
next reply other threads:[~2019-09-29 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 21:38 Robert Krig [this message]
2019-09-30 6:01 ` BTRFS Raid5 error during Scrub Nikolay Borisov
2019-09-30 9:37 ` Robert Krig
2019-10-01 18:10 ` Chris Murphy
2019-10-02 10:17 ` Robert Krig
2019-10-03 12:18 ` Robert Krig
2019-10-03 20:18 ` Chris Murphy
2019-10-04 10:00 ` Robert Krig
2019-09-30 9:56 ` [BTRFS " Graham Cobb
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=804e7e93a00dfe954222e4f8dc820a075d9ccb79.camel@render-wahnsinn.de \
--to=robert.krig@render-wahnsinn.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.