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 21:39:48 +1000 [thread overview]
Message-ID: <20120920213948.7dfc5f78@notabene.brown> (raw)
In-Reply-To: <CAFEwywZ58nJMxd9ae66fEsWcUo94Djvhj44fg3MxFcQp_7_vpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Thu, 20 Sep 2012 11:53:04 +0200 Markus Irle <tha.bear@gmail.com> wrote:
> Hi Neil,
>
> On Thu, Sep 20, 2012 at 1:11 AM, NeilBrown <neilb@suse.de> wrote:
> >
> > 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.
>
> Thanks, will try.
>
> Resyncing won't overwrite the existing data, will it?
No, it won't. It'll just check all the parity blocks are correct.
> Sorry for being overly cautious...
Not something to apologise for ....
NeilBrown
>
> Cheers,
> Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-20 11:39 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
2012-09-20 9:53 ` Markus Irle
2012-09-20 11:39 ` NeilBrown [this message]
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=20120920213948.7dfc5f78@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.