From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: recovery problem raid5
Date: Sat, 19 Mar 2016 00:39:29 +0000 (UTC) [thread overview]
Message-ID: <pan$11177$dc23156e$9ffc90e2$20c175e7@cox.net> (raw)
In-Reply-To: 20160318180207.GA1802@carfax.org.uk
Hugo Mills posted on Fri, 18 Mar 2016 18:02:07 +0000 as excerpted:
> Also, that kernel's not really all that good for a parity RAID
> array -- it's the very first one that had the scrub and replace
> implementation, so it's rather less stable with parity RAID than the
> later 4.x kernels. That's probably not the issue here, though.
>
> On Fri, Mar 18, 2016 at 06:41:32PM +0100, Marcin Solecki wrote:
>>
>> # uname -a Linux jarvis.home 4.5.0-1.el7.elrepo.x86_64
>>
>> # btrfs --version btrfs-progs v3.19.1
Umm... Hugo, look again. He's running current 4.5 kernel. It's the
btrfs-progs version that's v3.19.1 and thus old.
Marcin. You're kernel is current and should be fine. It's the older
kernels that have the most problems and 3.19 that was the first one with
parity-raid scrub and replace, so Hugo obviously just read your post
wrong.
Other than that, I'd normally trust Hugo's recommendations over any I
might offer, and mount -o degraded is indeed precisely what's supposed to
be used in a missing device situation, so I agree with him there.
You might consider upgrading userspace (btrfs-progs), as Hugo does have a
point, if he did make it about the wrong thing, and while a 3.19 era
userspace should work, given that full parity-raid support was very new
at that point, a current 4.4.1 userspace may well have a few more
bugfixes, tho I've not tracked the parity-raid support specifically
enough to know for sure if it has any that apply to that. But once he
figures out you were talking about 3.19.1 userspace, not 3.19.1 kernel,
Hugo will probably know more which if any parity-raid specific changes
have been made to btrfs-progs since 3.19, as well.
(Of course, the wiki has a short user-targeted description of what
changed in each btrfs-progs release as well, and I could look it up there
if wanted to, but so can you, and I'm using the older raid1, not parity-
raid, so I don't have the direct personal interest in that info that you
might, so...)
--
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-03-19 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:41 recovery problem raid5 Marcin Solecki
2016-03-18 18:02 ` Hugo Mills
2016-03-18 18:08 ` Marcin Solecki
2016-03-18 23:31 ` Chris Murphy
2016-03-18 23:34 ` Hugo Mills
2016-03-18 23:40 ` Chris Murphy
2016-03-19 8:21 ` Marcin Solecki
2016-03-19 0:39 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-29 11:24 Pierre-Matthieu anglade
2016-04-30 1:25 ` Duncan
2016-05-03 9:48 ` Pierre-Matthieu anglade
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$11177$dc23156e$9ffc90e2$20c175e7@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).