From: NeilBrown <neilb@suse.de>
To: "David F." <df7729@gmail.com>
Cc: John Stoffel <john@stoffel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Breaks LSI RAID on C600 chipset
Date: Thu, 21 May 2015 10:29:59 +1000 [thread overview]
Message-ID: <20150521102959.3b9760ed@notabene.brown> (raw)
In-Reply-To: <CAGRSmLsRr6dHKjOuZB5oy+BALKatJ96P3PMGB9r+oVcft75Z4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2755 bytes --]
On Mon, 18 May 2015 10:58:19 -0700 "David F." <df7729@gmail.com> wrote:
> Do you think the latest version at
> http://git.neil.brown.name/?p=mdadm.git;a=summary is stable enough to
> use? It definitely fixes the major issue (losing the raid config)
> from the prior version.
It should be OK. I'll probably make a 3.3.3 in a little while to make it
official.
NeilBrown
>
> On Wed, May 13, 2015 at 7:26 AM, David F. <df7729@gmail.com> wrote:
> > Thanks.
> >
> > 1) The update did fix the broken RAID. I can reboot and the RAID
> > mirror still exists after reboots.
> >
> > 2) I do want to report that on the first test, the reboot was clean.
> > On the second reboot there was a warning message about the BIOS
> > detecting "Inconsistent Timestamps" on one of the drives and something
> > about which CONFIG the BIOS would use. I didn't have time to get it
> > all jotted down. Whatever it used was still okay since the RAID
> > mirror was still there after that message.
> >
> >
> > On Tue, May 12, 2015 at 5:35 PM, NeilBrown <neilb@suse.de> wrote:
> >> On Mon, 11 May 2015 09:31:26 -0700 "David F." <df7729@gmail.com> wrote:
> >>
> >>> any progress or more information needed on this?
> >>>
> >>> On Mon, Apr 20, 2015 at 10:39 PM, David F. <df7729@gmail.com> wrote:
> >>> > If you need access to the system, a network kvm is available - or if
> >>> > you have a C600 based system, you should see the same problem there.
> >>> >
> >>> > On Fri, Apr 10, 2015 at 1:07 PM, David F. <df7729@gmail.com> wrote:
> >>> >> Okay, and to confirm, this is happening on other C600 based systems.
> >>> >> Boot to Linux with MDADM raid support and the raid is gone after
> >>> >> reboot.
> >>> >>
> >>> >> On Thu, Apr 9, 2015 at 5:50 PM, NeilBrown <neilb@suse.de> wrote:
> >>> >>> On Thu, 9 Apr 2015 14:13:05 -0700 "David F." <df7729@gmail.com> wrote:
> >>> >>>
> >>> >>>> Hello,
> >>> >>>>
> >>> >>>> I built a new system, installed new drives (no partitioning, just raw
> >>> >>>> new drives), configured RAID 1, boot to linux, created reports
> >>> >>>> attached. Rebooted and the system doesn't see any configured raid
> >>> >>>> drives (just the two raw drives).
> >>> >>>
> >>> >>> Thanks. I might take a look, but I would greatly prefer it if you kept the
> >>> >>> linux-raid list on the Cc.....
> >>> >>>
> >>> >>> NeilBrown
> >>> >>>
> >>
> >> I must confess that I haven't even looked at it.
> >> But I just saw and email on linux-raid from Martin Wilck:
> >>
> >> Subject: [PATCH] DDF: _write_super_to_disk: fix anchor header type
> >>
> >> which very likely fixes your problem. I've applied it and pushed out to
> >> git://neil.brown.name/mdadm/
> >>
> >> NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-05-21 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 0:25 Breaks LSI RAID on C600 chipset David F.
2015-04-04 1:47 ` John Stoffel
[not found] ` <CAGRSmLu5kEXA34mmHb5Q9+Fjmh5NFtRw2hrOrCDiOS4NR=5fvQ@mail.gmail.com>
[not found] ` <21792.11560.92731.222551@quad.stoffel.home>
[not found] ` <CAGRSmLt+1KJJHmMgoUHG0Dq0qg+38q5PRWnMNCRFg6qTa9s7gQ@mail.gmail.com>
[not found] ` <21795.3296.846489.199118@quad.stoffel.home>
[not found] ` <CAGRSmLtrp6Rh3pALL2Rr62jRRZQKFg-3SaV_AxubaHNhkeb0UA@mail.gmail.com>
[not found] ` <20150410105001.171d6683@notabene.brown>
2015-04-10 20:07 ` David F.
2015-04-21 5:39 ` David F.
2015-05-11 16:31 ` David F.
2015-05-13 0:35 ` NeilBrown
2015-05-13 14:26 ` David F.
2015-05-18 17:58 ` David F.
2015-05-21 0:29 ` NeilBrown [this message]
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=20150521102959.3b9760ed@notabene.brown \
--to=neilb@suse.de \
--cc=df7729@gmail.com \
--cc=john@stoffel.org \
--cc=linux-raid@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).