linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: degraded raid 6 (1 bad drive) showing up inactive, only spares
Date: Fri, 15 Jun 2012 22:37:40 +1000	[thread overview]
Message-ID: <20120615223740.22a76a9c@notabene.brown> (raw)
In-Reply-To: <4FDB1DF3.3080401@schinagl.nl>

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]

On Fri, 15 Jun 2012 13:35:15 +0200 Oliver Schinagl <oliver+list@schinagl.nl>
wrote:

> Neil,
> 
> Good read! I don't know if it's important to have a list of all affected 
> kernels, but as a Gentoo user, know that it affects at least the 
> unstable branch, but I would not be surprised if it even affects the 
> stable hardened kernel. I run those on my servers and may have noticed 
> that behavior on my arrays as well.

Thanks.

It would be useful adding other kernels, but only where a vendor has
backported the offending patch to an earlier release, and then I'd want
actual release numbers from the vendor.

So if you could show me how to decode the gentoo kernel package information
so I could see exactly what patches were in which release I could work out
the release numbers from that ....

Thanks,
NeilBrown


> 
> Oliver
> 
> On 15-06-12 09:37, NeilBrown wrote:
> > At the suggestion of Mikael Abrahamsson I have written
> >
> >    http://neil.brown.name/blog/20120615073245
> >
> > discussing this bug in detail.
> >
> > I'll probably post the whole thing to Linux RAID tomorrow, which a better
> > subject line.
> >
> > NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-06-15 12:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 11:55 degraded raid 6 (1 bad drive) showing up inactive, only spares Martin Ziler
2012-06-07 12:29 ` NeilBrown
     [not found]   ` <CAGHsWsm_Xvf59VCuHyJvoMW6peiFHK=YQKGzr3cq=RDk7jyqKg@mail.gmail.com>
2012-06-07 21:14     ` NeilBrown
     [not found]       ` <C9680CD3-8DA8-4FE3-8337-481676213C39@googlemail.com>
2012-06-09 22:09         ` NeilBrown
2012-06-07 21:16   ` Oliver Schinagl
2012-06-07 22:34     ` NeilBrown
     [not found]   ` <alpine.DEB.2.00.1206080743310.25054@uplift.swm.pp.se>
2012-06-15  7:37     ` NeilBrown
2012-06-15 11:35       ` Oliver Schinagl
2012-06-15 12:37         ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-17 15:52 Martin Ziler
2012-06-20 21:56 ` NeilBrown

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=20120615223740.22a76a9c@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    /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).