From: NeilBrown <neilb@suse.de>
To: Markus Irle <tha.bear@gmail.com>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: Wrong array size detected after reboot
Date: Thu, 20 Sep 2012 09:11:09 +1000 [thread overview]
Message-ID: <20120920091109.5d950820@notabene.brown> (raw)
In-Reply-To: <CAFEwywbuH1689UStqoGOsvAh_X9afCpojKouY=Po5sXFGDFutw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
On Wed, 19 Sep 2012 20:34:11 +0200 Markus Irle <tha.bear@gmail.com> wrote:
> Hi Neal,
>
> On Wed, Sep 19, 2012 at 3:42 AM, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 16 Sep 2012 01:32:06 +0200 Markus Irle <tha.bear@gmail.com> wrote:
> >
> >> I'm running 3.2 (3.2.0-31-generic, latest in current Ubuntu release 12.04) now.
> >
> > Sorry, I got that wrong.
> > That commit is the one that introduced the bug.
> >
> > It's fixed by 667a5313ecd7308d which will be in 3.6, and is being
> > back-ported to most -stable kernels, thought it doesn't seem to have arrived
> > in any yet.
> >
> > Maybe you can ask Ubuntu to provide a kernel containing that commit?
> > Or compile your own?
> >
> > Or find a kernel older than 3.2...
>
> Ok, I'm a bit confused.
Me too it would seem - sorry. I was thinking of a RAID0 problem with similar
symptoms.
>
> I was running 2.6.38 when I replaced the drives and grew the array.
> Apparently growing went fine, because I was using the array for a
> couple of weeks. But it didn't write the correct metadata (0.90), thus
> reassembling after boot fails (or rather is the wrong size).
>
> I tried booting with 3.0.0, 3.2.0 and 3.5.0 with exactly the same results.
>
> I feel that no matter what kernel, as long as the metadata's wrong, I
> can't assemble it correctly, correct?
Yes, the metadata has lots the most-significant-bit of the 'size'.
So it should be sufficient to:
mdadm -G /dev/md2 --size 2930266432
where the size is calculated as the current "used device size" plus 2^31.
You could probably just do "--size max"
This will cause a resync of the 2G of data which is probably unnecessary, but
is awkward to avoid.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-19 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 20:54 Wrong array size detected after reboot Markus Irle
2012-09-09 2:52 ` Phil Turmel
2012-09-09 23:13 ` NeilBrown
2012-09-15 23:32 ` Markus Irle
2012-09-19 1:42 ` NeilBrown
2012-09-19 18:34 ` Markus Irle
2012-09-19 23:11 ` NeilBrown [this message]
2012-09-20 9:53 ` Markus Irle
2012-09-20 11:39 ` NeilBrown
2012-10-13 19:15 ` Markus Irle
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=20120920091109.5d950820@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=tha.bear@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 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.