From: Martin Steigerwald <martin@lichtvoll.de>
To: John Center <jlcenter15@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub failing
Date: Fri, 01 Jan 2016 18:41:37 +0100 [thread overview]
Message-ID: <2990858.uJLD34QYPg@merkaba> (raw)
In-Reply-To: <26CBABB7-7744-4833-A37B-C2380304223F@gmail.com>
Am Freitag, 1. Januar 2016, 11:41:20 CET schrieb John Center:
Happy New Year!
> > On Jan 1, 2016, at 12:55 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> >
> >
> > 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 must have missed that, I'll check the list again to try & understand the
> issue better.
I had repeatedly failing scrubs as mentioned in another thread here, until I
used 4.4 kernel. With 4.3 kernel scrub also didn´t work. I didn´t use the
debug options you used above and I am not sure whether I had this scrub issue
with 4.2 already, so I am not sure it has been the same issue. But you may
need to run 4.4 kernel in order to get scrub working again.
See my thread "[4.3-rc4] scrubbing aborts before finishing" for details.
Thanks,
--
Martin
next prev parent reply other threads:[~2016-01-01 17:41 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
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 [this message]
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=2990858.uJLD34QYPg@merkaba \
--to=martin@lichtvoll.de \
--cc=jlcenter15@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox