linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <nfbrown@novell.com>
To: Liwei <xieliwei@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: RAID6 grow unexpected results
Date: Fri, 23 Oct 2015 09:37:05 +1100	[thread overview]
Message-ID: <87io5yzg1a.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAPE0SYz97qwHaQjgguZbQ3rdxKZjDdS9sg5F5dy10W3GP=U3+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

Liwei <xieliwei@gmail.com> writes:

> Hi list,
>     I tried growing a RAID6 array by executing the mdadm --add and
> mdadm --grow --raid-devices commands. Usually that should run fine and
> I can continue with pvresize.

That is incorrect.  You cannot run "pvresize" until the reshape
completes.

>
>     This time however, the actual usable raid array size did not
> change even though reshape begins. In my confusion, I decided to
> reboot. That didn't solve the problem (and apparently the reshape was
> interrupted, but mdadm shows the grown array as clean?)

Clean is expected.  It will be in an intermediate state, part has
reshaped to extra devices, part is still the original.

>
>     I then executed mdadm --grow --size=max, which seemed to have
> increased the array size, but apparently by too much. Now I'm getting
> "attempt to access beyond end of device" errors for each of the
> component drives. A new reshape operation has also begun, which I
> expect would fail as the array size is now too big.

"--size" isn't the same as "--array-size".
"--size" is the size of the component devices to use.

The "attempt to access beyond end of device" errors are unexpected but
presumably related o the "--size=max".  Maybe the 'max' chosen was too
large.  That suggests a bug somewhere.
You probably want to reduce that size back to where it was.

>
>     What did I do wrong and how can I remedy this?

Could we start with "mdadm --examine" status of all devices, "mdadm
--detail" of the array, and all kernel messages that could possibly
relate to the array since you first started this exercise?

NeilBrown

>
> Liwei
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2015-10-22 22:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 19:47 RAID6 grow unexpected results Liwei
2015-10-22 22:37 ` Neil Brown [this message]
2015-10-23  6:14   ` Liwei
2015-10-23  7:15     ` Neil Brown

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=87io5yzg1a.fsf@notabene.neil.brown.name \
    --to=nfbrown@novell.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=xieliwei@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).