On Wed, Jul 7, 2010 at 3:13 PM, Peter Jeremy <peter.jer...@alcatel-lucent.com> wrote: > On 2010-Jul-08 02:39:05 +0800, Garrett D'Amore <garr...@nexenta.com> wrote: >>I believe that long term folks are working on solving this problem. I >>believe bp_rewrite is needed for this work. > > Accepted. > >>Mid/short term, the solution to me at least seems to be to migrate your >>data to a new zpool on the newly configured array, etc. > > IMHO, this isn't an acceptable solution. > > Note that (eg) DEC/Compaq/HP AdvFS has supported vdev removal from day > 1 and (until a couple of years ago), I had an AdvFS pool that had, > over a decade, grown from a mirrored pair of 4.3GB disks to six pairs > of mirrored 36GB disks - without needing any downtime for disk > expansion. [Adding disks was done with mirror pairs because AdvFS > didn't support any RAID5/6 style redundancy, the big win was being > able to remove older vdevs so those disk slots could be reused].
None of that requires removing top-level vdevs, and is entirely possible with ZFS today: Create the initial pool: zpool create poolname mirror disk01 disk02 Add another mirror: zpool add poolname mirror disk03 disk04 Replace one of the drives with a larger on (this may not be perfectly correct, going from memory): zpool attach poolname disk05 disk01 zpool detach poolname disk01 Carry on with the add and replace methods as needed until you have your 6-mirror pool. No vdev removals required. -- Freddie Cash fjwc...@gmail.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
