linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Matthews <simon.d.matthews@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: Can't start array and Negative "Used Dev Size"
Date: Wed, 29 Jun 2011 20:15:12 -0700	[thread overview]
Message-ID: <BANLkTi=7EUhfN5ZWRXXNyEO=r+1q5DRDVA@mail.gmail.com> (raw)
In-Reply-To: <20110630102522.3dd9579d@notabene.brown>

Neil,

On Wed, Jun 29, 2011 at 5:25 PM, NeilBrown <neilb@suse.de> wrote:
> 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.
>

The system seems to take a long time to start one of the hard drives,
with many messages about doing resets. I am going to swap out the
mobile rack that the drive is installed in (it is limiting it to
1.5Gbps, instead of connecting at 3Gbps).

It still seems odd, because the other arrays that use partitions on
that disk start up.

Simon
--
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

  reply	other threads:[~2011-06-30  3:15 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
2011-06-30  3:15         ` Simon Matthews [this message]
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='BANLkTi=7EUhfN5ZWRXXNyEO=r+1q5DRDVA@mail.gmail.com' \
    --to=simon.d.matthews@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 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).