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: Wed, 19 Sep 2012 11:42:02 +1000 [thread overview]
Message-ID: <20120919114202.0ad6355b@notabene.brown> (raw)
In-Reply-To: <CAFEwywaGN3cvXVAJxsWuc1-j0mfeLtKs_iqNznFQN8QA7JO8qQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
On Sun, 16 Sep 2012 01:32:06 +0200 Markus Irle <tha.bear@gmail.com> wrote:
> Hi guys,
>
> Thanks for your help.
>
> On Mon, Sep 10, 2012 at 1:13 AM, NeilBrown <neilb@suse.de> wrote:
> > On Sat, 08 Sep 2012 22:52:18 -0400 Phil Turmel <philip@turmel.org> wrote:
>
> **snip**
>
> >> Until recently, due to a long-standing bug, devices larger than 2T were
> >> not usable with v0.90 meta-data. I don't remember precisely when that
> >> bug was fixed, but I believe it was in the past year. There are also
> >> potential identification problems with v0.90 when used on the last
> >> partition of a device, but you have a misalignment warning that would
> >> prevent that.
> >
> > The bug was fixed in 3.1-rc6, (commit 27a7b260f71439c40546)
>
> 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...
NeilBrown
>
> >> You should see that the used dev size is very close to 2TiB less than
> >> the actual size of your devices.
> >>
> >> First, try the latest stable mainline kernel that you can. That should
> >> let you back up your data.
>
> Unfortunately nothing's changed.
>
> The array still thinks it's small:
> [ 1.693557] --- level:5 rd:3 wd:3
> [ 1.693559] disk 0, o:1, dev:sdb1
> [ 1.693561] disk 1, o:1, dev:sdd1
> [ 1.693562] disk 2, o:1, dev:sde1
> [ 1.693593] md2: detected capacity change from 0 to 1603139141632
>
> and the vg doesn't start:
> [ 1.778499] device-mapper: table: 252:0: md2 too small for target:
> start=384, len=11721064448, dev_size=3131131136
>
> Cheers,
> Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-19 1:42 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 [this message]
2012-09-19 18:34 ` Markus Irle
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=20120919114202.0ad6355b@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.