Re: Raid 4 resize, raid0 limit question

["JaniD++" <djani22@dynamicweb.hu>]

----- Original Message ----- 
From: "Neil Brown" <neilb@suse.de>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-raid@vger.kernel.org>
Sent: Friday, February 03, 2006 1:12 AM
Subject: Re: Raid 4 resize, raid0 limit question


> On Friday February 3, djani22@dynamicweb.hu wrote:
> > Hello, list,
> >
> > I plan to resize (grow) one raid4 array.
> >
> > 1. stop the array.
> > 2. resize the partition on all disks to fit the maximum size.
>
> The approach is currently not supported.  It would need a change to
> mdadm to find the old superblock and relocate it to the new end of the
> partition.
>
> The only currently 'supported' way it to remove devices one at a time,
> resize them, and add them back in as new devices, waiting for the
> resync.

Good news! :-)
This takes about 1 weeks for me... :-(
I should recreate....


>
> NeilBrown
>
>
> >
> > After this restart(assemble) the array is possiple?
> > I mean, how can the kernel find the superblock fits on the half of the
new
> > partitions?
> > I need to recreate the array instead of using -G option?
> > Can i force raid to resync only the new area?
> >
> > The raid0 in 2.6.16-rc1 supports 4x 3.6TB soure devices? :-)
>
> ... maybe?
> I think it does, but I cannot promise anything.

Anyway, i will test it on the weekend, and i dont need to grow the FS too on
it.

How can i safe test it (and NBD >2TB) to work well, without data lost?

Thanks,
Janos

>
> NeilBrown
>
>
> >
> > Thanks,
> > Janos
> >
> > -
> > 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