Prasad Unnikrishnan wrote:
Add the new disk - start writing new blocks to that disk, instead of waiting to
re-layout all the stipes. And when the disk is not active, do slow/safe copy on
write to balance all the blocks?
Conceptually, yes, doing a zpool expansion while the pool is live isn't
hard to map out, conceptually.
As always, the devil is in the details. In this case, the primary
problem I'm having is maintaining two different block mapping schemes
(one for the old disk layout, and one for the new disk layout) and still
being able to interrupt the expansion process. My primary problem is
that I have to keep both schemes in memory during the migration, and if
something should happen (i.e. reboot, panic, etc) then I lose the
current state of the zpool, and everything goes to hell in a handbasket.
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
Timezone: US/Pacific (GMT-0800)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
