From: NeilBrown <neilb@suse.de>
To: Simon Matthews <simon.d.matthews@gmail.com>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: Can't start array and Negative "Used Dev Size"
Date: Thu, 30 Jun 2011 10:25:22 +1000 [thread overview]
Message-ID: <20110630102522.3dd9579d@notabene.brown> (raw)
In-Reply-To: <BANLkTin7f-8tLDoZsmyFocb9j1e1wn=4Dw@mail.gmail.com>
On Wed, 29 Jun 2011 08:45:33 -0700 Simon Matthews
<simon.d.matthews@gmail.com> wrote:
> Neil,
>
>
>
> On Tue, Jun 28, 2011 at 10:24 PM, Simon Matthews
> <simon.d.matthews@gmail.com> wrote:
> > Neil,
> >
> >
> >
> > On Tue, Jun 28, 2011 at 10:18 PM, NeilBrown <neilb@suse.de> wrote:
>
> >> mdadm -S /dev/md4
> >> mdadm -A /dev/md4 /dev/sdc1 /dev/sdd1 --verbose
> >
> > That solved it. The array started.
>
> Do you have any idea why the array did not start when the system
> booted? I also have an md6 on the same hard drives that was created at
> the same time as md4, but md6 started on the boot.
>
Not really ... I would need to see logs to be at all confident.
Based on the very limit info I have my best guess is that something -
probably udev - ran
mdadm --incremental /dev/sdc1
but didn't run
mdadm --incremental /dev/sdd1
I cannot imagine why it would do that though.
This would have the effect of leaving sdc1 as a member of md4, but md4 still
being inactive.
NeilBrown
--
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:[~2011-06-30 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 4:29 Can't start array and Negative "Used Dev Size" Simon Matthews
2011-06-29 5:18 ` NeilBrown
2011-06-29 5:24 ` Simon Matthews
2011-06-29 5:37 ` NeilBrown
2011-06-29 5:59 ` Simon Matthews
2011-06-29 6:18 ` NeilBrown
2011-06-29 15:45 ` Simon Matthews
2011-06-30 0:25 ` NeilBrown [this message]
2011-06-30 3:15 ` Simon Matthews
2011-07-02 4:41 ` Simon Matthews
2011-07-02 6:19 ` Simon Matthews
2011-07-04 5:45 ` Luca Berra
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=20110630102522.3dd9579d@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=simon.d.matthews@gmail.com \
/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).