From: Reuben Farrelly <reuben-lkml@reub.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: Resizing RAID-1 arrays - some possible bugs and problems
Date: Sat, 08 Jul 2006 09:10:07 +1200 [thread overview]
Message-ID: <44AECDAF.3080608@reub.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0607071451370.14371@p34.internal.lan>
On 8/07/2006 6:52 a.m., Justin Piszcz wrote:
> Reuben,
>
> What chunk size did you use?
>
> I can't even get mine to get past this part:
>
> p34:~# mdadm /dev/md3 --grow --raid-disks=7
> mdadm: Need to backup 15360K of critical section..
> mdadm: Cannot set device size/shape for /dev/md3: No space left on device
>
> Justin.
>
Just whatever the system selected for the chunk size, ie I didn't specify it
myself ;)
[root@tornado cisco]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc2[0] sda2[1]
24410688 blocks [2/2] [UU]
bitmap: 0/187 pages [0KB], 64KB chunk
md1 : active raid1 sdc3[0] sda3[1]
19542944 blocks [2/2] [UU]
bitmap: 0/150 pages [0KB], 64KB chunk
md2 : active raid1 sdc5[0] sda5[1]
4891648 blocks [2/2] [UU]
bitmap: 2/150 pages [8KB], 16KB chunk
I was working on md1 when I filed the email earlier.
I wonder if the chunk size is left as-is after a --grow, and if this is optimal
or not or if this could lead to issues...
reuben
next prev parent reply other threads:[~2006-07-07 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 13:40 Resizing RAID-1 arrays - some possible bugs and problems Reuben Farrelly
2006-07-07 18:52 ` Justin Piszcz
2006-07-07 21:10 ` Reuben Farrelly [this message]
2006-07-07 22:12 ` Neil Brown
2006-07-07 22:58 ` Reuben Farrelly
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=44AECDAF.3080608@reub.net \
--to=reuben-lkml@reub.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.