From: Martin Wilck <mwilck@arcor.de>
To: "David F." <df7729@gmail.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: MDADM 3.3 broken?
Date: Thu, 21 Nov 2013 21:50:10 +0100 [thread overview]
Message-ID: <528E7202.9020301@arcor.de> (raw)
In-Reply-To: <CAGRSmLsCdXbAUCUMncKv1ER9HBtFnk9BeuF6iaWv=9SSRAiHeA@mail.gmail.com>
On 11/21/2013 12:15 AM, David F. wrote:
> mdadm: /dev/sdf is identified as a member of /dev/md/ddf0, slot 4.
> mdadm: /dev/sde is identified as a member of /dev/md/ddf0, slot 3.
> mdadm: /dev/sdd is identified as a member of /dev/md/ddf0, slot 2.
> mdadm: /dev/sdc is identified as a member of /dev/md/ddf0, slot 1.
> mdadm: /dev/sdb is identified as a member of /dev/md/ddf0, slot 0.
> mdadm: ignoring /dev/sdb as it reports /dev/sdf as failed
> mdadm: ignoring /dev/sdc as it reports /dev/sdf as failed
> mdadm: ignoring /dev/sdd as it reports /dev/sdf as failed
> mdadm: ignoring /dev/sde as it reports /dev/sdf as failed
> mdadm: no uptodate device for slot 0 of /dev/md/ddf0
> mdadm: no uptodate device for slot 2 of /dev/md/ddf0
> mdadm: no uptodate device for slot 4 of /dev/md/ddf0
> mdadm: no uptodate device for slot 6 of /dev/md/ddf0
> mdadm: added /dev/sdf to /dev/md/ddf0 as 4
> mdadm: Container /dev/md/ddf0 has been assembled with 1 drive (out of 5)
That looks really weird. The (healthy?) devices sdb-sde are ignored
because they report sdf as failed, and then sdf is used for assembly?
I have no idea at the moment, I need to read the code.
> Output of dmraid --raid_devices command:
> /dev/sdf: ddf1, ".ddf1_disks", GROUP, unknown, 285155328 sectors, data@ 0
> /dev/sde: ddf1, ".ddf1_disks", GROUP, ok, 285155328 sectors, data@ 0
> /dev/sdd: ddf1, ".ddf1_disks", GROUP, ok, 285155328 sectors, data@ 0
> /dev/sdc: ddf1, ".ddf1_disks", GROUP, ok, 285155328 sectors, data@ 0
> /dev/sdb: ddf1, ".ddf1_disks", GROUP, ok, 285155328 sectors, data@ 0
This seems to support then notion that something's wrong with /dev/sdf.
Martin
next prev parent reply other threads:[~2013-11-21 20:50 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
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 [this message]
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=528E7202.9020301@arcor.de \
--to=mwilck@arcor.de \
--cc=df7729@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.