linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Irle <tha.bear@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: Wrong array size detected after reboot
Date: Wed, 19 Sep 2012 20:34:11 +0200	[thread overview]
Message-ID: <CAFEwywbuH1689UStqoGOsvAh_X9afCpojKouY=Po5sXFGDFutw@mail.gmail.com> (raw)
In-Reply-To: <20120919114202.0ad6355b@notabene.brown>

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.

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?

Cheers,
Marks.

  reply	other threads:[~2012-09-19 18:34 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 [this message]
2012-09-19 23:11           ` NeilBrown
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='CAFEwywbuH1689UStqoGOsvAh_X9afCpojKouY=Po5sXFGDFutw@mail.gmail.com' \
    --to=tha.bear@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=philip@turmel.org \
    /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).