From: Tyson Whitehead <twhitehead@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Scrub aborts on newer kernels
Date: Mon, 20 Jun 2016 05:22:54 -0400 [thread overview]
Message-ID: <5767B5EE.30409@gmail.com> (raw)
In-Reply-To: <CAJCQCtQ8yPE5CSyrZ2k0ZCT6Wp5VYo9iSxe9znKv=Q04cXzODw@mail.gmail.com>
On 17/06/16 06:18 PM, Chris Murphy wrote:
> On Fri, Jun 17, 2016 at 8:45 AM, Tyson Whitehead <twhitehead@gmail.com> wrote:
>> On May 27, 2016 12:12:54 PM Chris Murphy wrote:
>>> On Thu, May 26, 2016 at 11:55 AM, Tyson Whitehead <twhitehead@gmail.com> wrote:
>>>> Under the last several kernels versions (4.6 and I believe 4.4 and, 4.5) btrfs scrub aborts before completing.
>>>
>>> I can't reproduce this with btrfs-progs 4.5.2 and kernel 4.6.0.
>>>
>>> I think the bigger issue is the lack of information why a scrub is aborted.
>>
>> Thanks for checking into this Chris.
>>
>> Any advice on how to get some more information out of the scrub process?
>
> Next you need to find out why this one device has so many errors. Put the output from smartctl -x /dev/sdb somewhere, maybe even attach it to the bug report since it's somewhat related. Either that device is simply unreliable, or you've got a bad cable connection.
The device is okay. The errors were caused by me running it for a period with only one of the devices present.
In more detail. My desktop has a BTRFS RAID 1 setup. I needed to access to it on the road, so I just shut the desktop down, grabbed one of the drives, and used it in my laptop in degraded mode.
When I got back I recombined them (the one I left in my office was never booted by itself) and started a scrub. That is when I discovered scrub aborted on newer kernels but completed okay on older ones.
Cheers! -Tyson
next prev parent reply other threads:[~2016-06-20 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 17:55 Scrub aborts on newer kernels Tyson Whitehead
2016-05-27 18:12 ` Chris Murphy
2016-06-17 14:45 ` Tyson Whitehead
2016-06-17 22:18 ` Chris Murphy
2016-06-17 22:20 ` Chris Murphy
2016-06-20 9:22 ` Tyson Whitehead [this message]
2016-06-20 18:05 ` Chris Murphy
2016-06-20 18:06 ` Chris Murphy
2016-06-17 22:00 ` 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=5767B5EE.30409@gmail.com \
--to=twhitehead@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.