From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Saint Germain <saintger@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel bug during RAID1 replace
Date: Mon, 27 Jun 2016 16:58:37 -0600 [thread overview]
Message-ID: <CAJCQCtRm3=7fkBcTA4o4r10cLqC-bzcsKunb5k+uA-siyZmMnQ@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtR3FQ-Pe40dOcKGgd+8paraHuCoNCw5Kk+2G7bOOJF1rw@mail.gmail.com>
On Mon, Jun 27, 2016 at 4:55 PM, Chris Murphy <lists@colorremedies.com> wrote:
>> BTRFS info (device sdb1): dev_replace from /dev/sda1 (devid 1) to /dev/sdd1 started
>> scrub_handle_errored_block: 166 callbacks suppressed
>> BTRFS warning (device sdb1): checksum error at logical 93445255168 on dev /dev/sda1, sector 77669048, root 5, inode 3434831, offset 479232, length 4096, links 1 (path: user/.local/share/zeitgeist/activity.sqlite-wal)
>> btrfs_dev_stat_print_on_error: 166 callbacks suppressed
>> BTRFS error (device sdb1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 14221, gen 24
>> scrub_handle_errored_block: 166 callbacks suppressed
>> BTRFS error (device sdb1): unable to fixup (regular) error at logical 93445255168 on dev /dev/sda1
>
> Shoot. You have a lot of these. It looks suspiciously like you're
> hitting a case list regulars are only just starting to understand
Forget this part completely. It doesn't affect raid1. I just re-read
that your setup is not raid1, I don't know why I thought it was raid5.
The likely issue here is that you've got legit corruptions on sda (mix
of slow and flat out bad sectors), as well as a failing drive.
This is also safe to issue:
smartctl -l scterc /dev/sda
smartctl -l scterc /dev/sdb
cat /sys/block/sda/device/timeout
cat /sys/block/sdb/device/timeout
--
Chris Murphy
next prev parent reply other threads:[~2016-06-27 22:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 21:36 Kernel bug during RAID1 replace Saint Germain
2016-06-27 21:42 ` Chris Murphy
2016-06-27 22:26 ` Saint Germain
2016-06-27 22:55 ` Chris Murphy
2016-06-27 22:58 ` Chris Murphy [this message]
2016-06-27 23:06 ` Saint Germain
2016-06-28 0:00 ` Chris Murphy
2016-06-28 0:10 ` Chris Murphy
2016-06-28 0:49 ` Saint Germain
2016-06-28 2:14 ` Chris Murphy
2016-06-28 22:52 ` Saint Germain
2016-06-29 4:25 ` Chris Murphy
2016-06-29 9:50 ` Saint Germain
2016-06-29 17:28 ` Chris Murphy
2016-06-29 18:12 ` Saint Germain
2016-06-29 18:19 ` Austin S. Hemmelgarn
2016-06-29 19:02 ` Saint Germain
2016-06-29 19:08 ` Chris Murphy
2016-06-29 19:16 ` Saint Germain
2016-06-29 19:23 ` Hugo Mills
2016-06-29 23:51 ` Saint Germain
2016-06-30 0:24 ` Chris Murphy
2016-06-30 21:02 ` Saint Germain
2016-06-30 0:19 ` Chris Murphy
2016-06-29 17:41 ` Saint Germain
2016-06-27 23:03 ` Saint Germain
2016-06-27 23:49 ` 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='CAJCQCtRm3=7fkBcTA4o4r10cLqC-bzcsKunb5k+uA-siyZmMnQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=saintger@gmail.com \
/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).