From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub failing
Date: Fri, 1 Jan 2016 05:55:08 +0000 (UTC) [thread overview]
Message-ID: <pan$1f21$8d293d0$5b6cd545$34c90ade@cox.net> (raw)
In-Reply-To: CAPgWCbQ9HS1N=JCbbHuT9yyTz3JPAizA+DvOAR7_GX73CVix0g@mail.gmail.com
John Center posted on Thu, 31 Dec 2015 11:20:28 -0500 as excerpted:
> I run a weekly scrub, using Marc Merlin's btrfs-scrub script.
> Usually, it completes without a problem, but this week it failed. I ran
> the scrub manually & it stops shortly:
>
> john@mariposa:~$ sudo /sbin/btrfs scrub start -BdR /dev/md124p2
> ERROR: scrubbing /dev/md124p2 failed for device id 1:
> ret=-1, errno=5 (Input/output error)
> scrub device /dev/md124p2 (id 1) canceled
> scrub started at Thu Dec 31 00:26:34 2015
> and was aborted after 00:01:29 [...]
> My Ubuntu 14.04 workstation is using the 4.2 kernel (Wily).
> I'm using btrfs-tools v4.3.1. [...]
A couple months ago, which would have made it around the 4.2 kernel
you're running (with 4.3 being current and 4.4 nearly out), there were a
number of similar scrub aborted reports on the list.
I don't recall seeing any directly related patches, but the reports died
down, whether because everybody having them had reported already, or
because a newer kernel fixed the problem, I'm not sure, as I never had
the problem myself[1].
So I'd suggest upgrading to either the current 4.3 kernel or the latest
4.4-rc, and hopefully the problem will be gone. If I'd had the problem
myself I could tell you for sure whether it went away for me with 4.3,
but as I didn't...
In any event, the 4.2 kernel wasn't a long-term-support kernel anyway.
4.1 was and 4.4 is scheduled to be. So upstream 4.2 updates should be
ended or coming to an end in any case, and an upgrade (or possibly
downgrade to the LTS 4.1) is recommended anyway, tho of course Ubuntu
could be doing its own support, independent of upstream, but then you'd
need to get support from them as upstream won't be tracking patches
they've backported and thus can't provide proper support.
---
[1] All my btrfs are relatively small, under 50 GiB per device, and on
SSD, so scrubs normally complete in under a minute, while your report of
scrub aborting after a minute and a half was typical, so it's likely my
scrubs were simply done before whatever the problem was could trigger.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-01-01 5:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 16:20 btrfs scrub failing John Center
2016-01-01 5:55 ` Duncan [this message]
2016-01-01 16:41 ` John Center
2016-01-01 17:05 ` Duncan
2016-01-01 18:31 ` John Center
2016-01-02 1:04 ` John Center
2016-01-02 4:04 ` John Center
2016-01-02 4:49 ` John Center
2016-01-02 10:35 ` Martin Steigerwald
2016-01-02 11:41 ` Martin Steigerwald
[not found] ` <CAPgWCbQE4aJEQ_vR2vu_ad1v2dH6A=50iUSGnQgNeA4Qo68iSQ@mail.gmail.com>
2016-01-03 9:57 ` Martin Steigerwald
2016-01-01 17:41 ` Martin Steigerwald
2016-01-01 18:20 ` John Center
2016-01-01 19:54 ` Martin Steigerwald
[not found] ` <CAPgWCbTPMqCDx99vBXqFsCAjLzCsnxvCwFQnRfSymbD-_RssMA@mail.gmail.com>
[not found] ` <CAPgWCbRZOT-LvECuqgbaHSKWE8mYiO5R9kvk-8BeL-9Lb85fVA@mail.gmail.com>
2016-01-03 10:06 ` Martin Steigerwald
2016-01-03 22:16 ` John Center
2016-01-03 22:33 ` John Center
2016-01-03 22:43 ` Martin Steigerwald
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='pan$1f21$8d293d0$5b6cd545$34c90ade@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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).