Brandon High <bh...@freaks.com> writes: > On Mon, Apr 12, 2010 at 7:38 AM, Harry Putnam <rea...@newsguy.com> wrote: >> But as someone suggested it might be better to get two more bigger >> drives. 1t or 1.5t would handle all my data on one pair. >> >> Then I guess after moving all the data to a single zpool made up of >> those 2 new disks, I could then add the freed up drives as vdevs to >> it?
First off I'm sorry to keep on with what are actually theoretical questions since I'm chicken to work along with this with real experiments etc.... It may get a little irritating answering things that might be obvious if I just tried this stuff as I go allong. But, I'm too unskilled in solaris and zfs admin to be risking a total melt down if I try that before gaining a more thorough understanding. > It's probably even easier than that if you have enough ports and bays > for two more drives. What you'd have to do, roughly, is: > > 1. Add both of the new drives as additional mirrors of the z2 pool. > Wait for resilver to complete. > 2. Detach the original drives from z2. If autoexpand is set to on, z2 > should now have 1.5TB. Otherwise export / import the pool. > 3. Add the original drives to z2 as a mirror vdev. I'm getting a bit confused here. If its possible to add a mirrored set as a vdev to a zpool like what seems to be happening in (3) above, why wouldn't I just add the two new disks as mirrored vdev to z2 to start off, rather than additional mirrors, and never remove the original disks of z2. > 4. Do a zfs send of all datasets from z3 to z2. > 5. zpool destroy z3. > 6. Add the drives from z3 to z2 a mirror vdev. [...] > If you're so inclined, you could move some datasets from rpool to z2 > to keep your rpool smaller. So having some data on rpool (besides the OS I mean) is not necessarily a bad thing then? _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
