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: Wed, 29 Jun 2011 15:18:25 +1000 [thread overview]
Message-ID: <20110629151825.56cb4499@notabene.brown> (raw)
In-Reply-To: <BANLkTincbuZrS3PuPBOgjidsR8jdyTGBRw@mail.gmail.com>
On Tue, 28 Jun 2011 21:29:37 -0700 Simon Matthews
<simon.d.matthews@gmail.com> wrote:
> Problem 1: "Used Dev Size"
> ====================
> Note: the system is a Gentoo box, so perhaps I have missed a kernel
> configuration option or use flag to deal with large hard drives.
>
> A week or two ago, I resized a raid1 array using 2x3TB drives. I went
Oopps. That array is using 0.90 metadata which can only handle up to 2TB
devices. The 'resize' code should catch that you are asking the impossible,
but it doesn't it seems.
You need to simply recreate the array as 1.0.
i.e.
mdadm -S /dev/md5
mdadm -C /dev/md5 --metadata 1.0 -l1 -n2 --assume-clean
Then all should be happiness.
>
> Problem 2: Can't start array
> ====================
> Whatever I do, I can't start md4:
> mdadm /dev/md4 --assemble
> mdadm: /dev/md4 is already in use.
>
> /proc/mdadm:
> md4 : inactive sdc1[0](S)
> 58591232 blocks super 1.2
What do you get if you:
mdadm -S /dev/md4
mdadm -A /dev/md4 /dev/sdc1 /dev/sdd1 --verbose
??
NeilBrown
next prev parent reply other threads:[~2011-06-29 5:18 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 [this message]
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
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=20110629151825.56cb4499@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).