linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Center <jlcenter15@gmail.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub failing
Date: Fri, 1 Jan 2016 13:20:49 -0500	[thread overview]
Message-ID: <91318630-E23C-495D-B70E-BB484B3721C6@gmail.com> (raw)
In-Reply-To: <2990858.uJLD34QYPg@merkaba>

Hi Martin,

Happy New Year!

> On Jan 1, 2016, at 12:41 PM, Martin Steigerwald <martin@lichtvoll.de> wrote:
> 
> 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:
>>> 
>>> 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.
> 
I was afraid of this. I just read your thread. I generally try to stay away from kernels so new, but I may have to try it. Was there any reason you didn't go to 4.1 instead?  (I run win8.1 in VirtualBox 5.0.12, when I need to run somethings under Windows. I'd have to wait until 4.4 is released & supported to do that.)

Thanks. 

    -John

  reply	other threads:[~2016-01-01 18:20 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
2016-01-01 18:20       ` John Center [this message]
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=91318630-E23C-495D-B70E-BB484B3721C6@gmail.com \
    --to=jlcenter15@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    /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).