Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Unable to grow raid10 (error -22)
Date: Wed, 25 Apr 2012 20:56:56 +1000	[thread overview]
Message-ID: <20120425205656.546af088@notabene.brown> (raw)
In-Reply-To: <4F97B003.1060201@rabbit.us>

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

On Wed, 25 Apr 2012 10:04:19 +0200 Peter Rabbitson <rabbit+list@rabbit.us>
wrote:

> I am facing a problem which I believe is new (I distinctly remember
> doing the same on 2.6.somethingold couple years ago). When I try to
> grow an array where all memembers have been replaced with large ones
> I get an inexplicable.
> 
>    kernel: md: couldn't update array info. -22
> 
> Nothing else. I am using kernel 3.2.0 and mdadm 3.2.3, both from
> debian:
> http://packages.debian.org/sid/linux-image-3.2.0-2-amd64 (3.2.15-1)
> http://packages.debian.org/sid/mdadm (3.2.3-2)
> 
> Here is my full test setup replicating the problem (was replicated
> on a different machine). Let me know if I can assist further in
> figuring this out:
> 
> root@Thesaurus:~/raidfail# for n in $(seq 4) ; do dd if=/dev/zero of=member_$n.img bs=1M count=256 ; done
> 
> root@Thesaurus:~/raidfail# for n in $(seq 4) ; do losetup /dev/loop$n member_$n.img ; done
> 
> root@Thesaurus:~/raidfail# losetup -a
> /dev/loop1: [fd01]:1081442 (/root/raidfail/member_1.img)
> /dev/loop2: [fd01]:1081481 (/root/raidfail/member_2.img)
> /dev/loop3: [fd01]:1081483 (/root/raidfail/member_3.img)
> /dev/loop4: [fd01]:1081515 (/root/raidfail/member_4.img)
> 
> root@Thesaurus:~/raidfail# mdadm -C /dev/md1010 -l 10 -p f3 -n 4 -c 256 -e 1.2 -z 128M /dev/loop[1234]
> mdadm: largest drive (/dev/loop1) exceeds size (131072K) by more than 1%
> Continue creating array? y
> mdadm: array /dev/md1010 started.
> 
> root@Thesaurus:~/raidfail# mdadm -w /dev/md1010
> 
> root@Thesaurus:~/raidfail# cat /proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4] [raid10]
> md1010 : active raid10 loop4[3] loop3[2] loop2[1] loop1[0]
>        174080 blocks super 1.2 256K chunks 3 far-copies [4/4] [UUUU]
                                             ^^^^^^^^^^^^

You cannot resize a 'far' RAID10.
In fact in 3.2 you cannot resize *any* RAID10.  That is only available in
3.4-rc, and even then only for 'near' and 'offset' layouts.



> 
> (Note - no bitmaps, no anything)
> 
> root@Thesaurus:~/raidfail# mdadm --grow --size=max /dev/md1010
> mdadm: Cannot set device size for /dev/md1010: Invalid argument

So here, "Invalid argument" means you asked it to do something that it cannot
do - your request was invalid.

NeilBrown



> 
> 
> root@Thesaurus:~/raidfail# tail /var/log/kern.log
> Apr 25 09:52:36 localhost kernel: md: using maximum available idle IO bandwidth (but not more than 30000 KB/sec) for resync.
> Apr 25 09:52:36 localhost kernel: md: using 128k window, over a total of 174080k.
> Apr 25 09:52:42 localhost kernel: md: md1010: resync done.
> Apr 25 09:52:43 localhost kernel: RAID10 conf printout:
> Apr 25 09:52:43 localhost kernel: --- wd:4 rd:4
> Apr 25 09:52:43 localhost kernel: disk 0, wo:0, o:1, dev:loop1
> Apr 25 09:52:43 localhost kernel: disk 1, wo:0, o:1, dev:loop2
> Apr 25 09:52:43 localhost kernel: disk 2, wo:0, o:1, dev:loop3
> Apr 25 09:52:43 localhost kernel: disk 3, wo:0, o:1, dev:loop4
> Apr 25 09:53:39 localhost kernel: md: couldn't update array info. -22
> 
> 
> root@Thesaurus:~/raidfail# mdadm -D /dev/md1010
> /dev/md1010:
>          Version : 1.2
>    Creation Time : Wed Apr 25 09:52:24 2012
>       Raid Level : raid10
>       Array Size : 174080 (170.03 MiB 178.26 MB)
>    Used Dev Size : 130560 (127.52 MiB 133.69 MB)
>     Raid Devices : 4
>    Total Devices : 4
>      Persistence : Superblock is persistent
> 
>      Update Time : Wed Apr 25 09:52:43 2012
>            State : clean
>   Active Devices : 4
> Working Devices : 4
>   Failed Devices : 0
>    Spare Devices : 0
> 
>           Layout : far=3
>       Chunk Size : 256K
> 
>             Name : Thesaurus:1010  (local to host Thesaurus)
>             UUID : 19aeca84:142ee179:b344a19d:08a730fc
>           Events : 17
> 
>      Number   Major   Minor   RaidDevice State
>         0       7        1        0      active sync   /dev/loop1
>         1       7        2        1      active sync   /dev/loop2
>         2       7        3        2      active sync   /dev/loop3
>         3       7        4        3      active sync   /dev/loop4
> 
> root@Thesaurus:~/raidfail# mdadm -E /dev/loop1
> /dev/loop1:
>            Magic : a92b4efc
>          Version : 1.2
>      Feature Map : 0x0
>       Array UUID : 19aeca84:142ee179:b344a19d:08a730fc
>             Name : Thesaurus:1010  (local to host Thesaurus)
>    Creation Time : Wed Apr 25 09:52:24 2012
>       Raid Level : raid10
>     Raid Devices : 4
> 
>   Avail Dev Size : 522240 (255.04 MiB 267.39 MB)
>       Array Size : 261120 (127.52 MiB 133.69 MB)
>    Used Dev Size : 261120 (127.52 MiB 133.69 MB)
>      Data Offset : 2048 sectors
>     Super Offset : 8 sectors
>            State : clean
>      Device UUID : d7734a6c:5df0c7cc:b5f7dc04:6595a5eb
> 
>      Update Time : Wed Apr 25 09:53:05 2012
>         Checksum : 22c8ad18 - correct
>           Events : 17
> 
>           Layout : far=3
>       Chunk Size : 256K
> 
>     Device Role : Active device 0
>     Array State : AAAA ('A' == active, '.' == missing)
> --
> 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: 828 bytes --]

  reply	other threads:[~2012-04-25 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25  8:04 Unable to grow raid10 (error -22) Peter Rabbitson
2012-04-25 10:56 ` NeilBrown [this message]
2012-04-25 11:10   ` Peter Rabbitson

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=20120425205656.546af088@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=rabbit+list@rabbit.us \
    /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