From: Martin Wilck <mwilck@arcor.de>
To: "David F." <df7729@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: MDADM 3.3 broken?
Date: Mon, 18 Nov 2013 21:22:57 +0100 [thread overview]
Message-ID: <528A7721.8080604@arcor.de> (raw)
In-Reply-To: <CAGRSmLviYJtCfNiARKW0FvrJ0BUDrvhPnQy2drzbkf95-Gfpag@mail.gmail.com>
On 11/18/2013 07:26 PM, David F. wrote:
> Hi,
>
> we updated our linux disk with mdadm 3.3 from 3.2.6 and customers are
> finding their RAID is no longer detected. It's only been a couple
> weeks and based on the number of customers, we know there is an issue.
> We're having those with problems workaround by having them load
> dmraid instead for now.
>
> We also did tests locally and finding intermittent problems with
> RAID-0 on ISW - sometimes 3.3 doesn't identify both drives as RAID
> members. 3.2.6 works 100% of the time.
>
> Also with DDF RAID - cisco server for example not detecting RAID5 -
> C220M3_LFF_SpecSheet.pdf. I believe they are using the LSI MegaRaid
> since DMRAID reports that.
Could you please provide mdadm -E and possibly mdadm --dump output of
the disks that aren't detected? How does RAID discovery work on your
systems? Are you using standard udev rules or something special? How
does your mdadm.conf look like?
Regards
Martin
>
> Are these problems known - we wouldn't mind moving to the latest
> version if your pretty sure it fixes it, otherwise we're going to have
> to revert to 3.2.6?
>
> TIA!!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-18 20:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 18:26 MDADM 3.3 broken? David F.
2013-11-18 20:22 ` Martin Wilck [this message]
2013-11-18 23:13 ` David F.
2013-11-19 0:01 ` NeilBrown
2013-11-19 17:05 ` David F.
2013-11-19 20:38 ` Martin Wilck
2013-11-19 22:34 ` David F.
2013-11-19 22:49 ` David F.
2013-11-19 19:45 ` Martin Wilck
2013-11-19 20:08 ` David F.
2013-11-19 23:51 ` NeilBrown
2013-11-20 0:22 ` David F.
2013-11-20 0:35 ` David F.
2013-11-20 0:48 ` NeilBrown
2013-11-20 1:29 ` David F.
2013-11-20 1:34 ` David F.
2013-11-20 2:30 ` NeilBrown
2013-11-20 6:41 ` David F.
2013-11-20 23:15 ` David F.
2013-11-21 20:50 ` Martin Wilck
2013-11-21 21:10 ` David F.
2013-11-21 21:30 ` Martin Wilck
2013-11-21 22:39 ` David F.
2013-11-25 21:39 ` Martin Wilck
2013-11-21 20:46 ` Martin Wilck
2013-11-21 21:06 ` David F.
2013-11-21 23:05 ` David F.
2013-11-21 23:09 ` David F.
2013-11-22 3:06 ` David F.
2013-11-22 18:36 ` David F.
2013-11-23 23:36 ` David F.
2013-11-25 21:56 ` Martin Wilck
2013-11-26 0:24 ` David F.
2013-11-26 21:59 ` David F.
2013-11-27 22:40 ` Martin Wilck
2013-12-06 1:53 ` David F.
2013-12-07 2:28 ` David F.
2013-12-07 3:16 ` NeilBrown
2013-12-07 3:46 ` David F.
2013-12-14 21:01 ` David F.
2014-01-20 4:34 ` NeilBrown
2014-01-20 21:52 ` Martin Wilck
2014-01-20 23:54 ` David F.
2014-01-22 22:32 ` David F.
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=528A7721.8080604@arcor.de \
--to=mwilck@arcor.de \
--cc=df7729@gmail.com \
--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).