From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Marcin Solecki <solo@alfazone.pl>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: recovery problem raid5
Date: Fri, 18 Mar 2016 23:34:22 +0000 [thread overview]
Message-ID: <20160318233422.GC1802@carfax.org.uk> (raw)
In-Reply-To: <CAJCQCtQyyk3XnyCBW0vij1RSypYXF7yEAhBqaztzmXMvMU=0ng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Fri, Mar 18, 2016 at 05:31:51PM -0600, Chris Murphy wrote:
> On Fri, Mar 18, 2016 at 12:02 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> > The main thing you haven't tried here is mount -o degraded, which
> > is the thing to do if you have a missing device in your array.
> >
> > 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.
>
>
> It's a 4.5.0 kernel with 3.19 progs. I'd update the progs even though
> that's unlikely the problem.
Oh, my mistake. I misread the 3.19 as the kernel version.
Marcin: Stick with the 4.5 kernel.
Hugo.
--
Hugo Mills | Yes, this is an example of something that becomes
hugo@... carfax.org.uk | less explosive as a one-to-one cocrystal with TNT.
http://carfax.org.uk/ | (Hexanitrohexaazaisowurtzitane)
PGP: E2AB1DE4 | Derek Lowe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-03-18 23:34 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 [this message]
2016-03-18 23:40 ` Chris Murphy
2016-03-19 8:21 ` Marcin Solecki
2016-03-19 0:39 ` Duncan
-- 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=20160318233422.GC1802@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=solo@alfazone.pl \
/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).