From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub failing
Date: Fri, 1 Jan 2016 17:05:55 +0000 (UTC) [thread overview]
Message-ID: <pan$ddf92$7633f36c$14118b68$b87353e3@cox.net> (raw)
In-Reply-To: 26CBABB7-7744-4833-A37B-C2380304223F@gmail.com
John Center posted on Fri, 01 Jan 2016 11:41:20 -0500 as excerpted:
> Ok, I'll upgrade to 4.3 & see if that resolves the problem with
> scrubbing.
> I was wondering when I compiled the btrfs-tools if there would be a
> problem with them not being in sync with the major kernel version.
FWIW newer (or older either, as long as not too old and you don't need
any of the features not in the older, and you're not trying to fix
problems only the newer can deal with) versions of btrfs-progs should be
fine. As a rule of thumb I recommend staying at least current to kernel
version, but that's a rule of thumb, primarily to prevent getting /too/
old, only. Both the btrfs-progs userspace and the kernel itself are
normally designed to be able to work with both older and newer versions
of the other one.
So userspace not being in sync with the kernel version shouldn't be a
problem.
> If this doesn't resolve the problem, what would you recommend my next
> steps should be? I've been hesitant to run too many of the btrfs-tools,
> mainly because I don't want to accidentally screw things up & I don't
> always know how to interpret the results. (I ran btrfs-debug-tree,
> hoping something obvious would show up. Big mistake. 😋)
LOLed at that debug-tree remark. Been there (with other tools) myself.
Well, I'm hoping someone who had the problem can confirm whether it's
fixed in current kernels (scrub is one of those userspace commands that's
mostly just a front-end to the kernel code which does the real work, so
kernel version is the important thing for scrub). I'm guessing so, and
that you'll find the problem gone in 4.3.
We'll cross the not-gone bridge if we get to it, but again, if the other
people who had the similar problem can confirm whether it disappeared for
them with the new kernel, it would help a lot, as there were enough such
reports that if it's the same problem and still there for everyone (which
I doubt as I expect there'd still be way more posts about it if so, but
confirmation's always good), nothing to do but wait for a fix, while if
not, and you still have your problem, then it's a different issue and the
devs will need to work with you on a fix specific to your problem.
--
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 17:06 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 [this message]
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$ddf92$7633f36c$14118b68$b87353e3@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 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.