Actually, I'm using ZFS in a SAN environment often importing LUNS to save
management overhead and make snapshots easily available, among other things. I
would love zfs remove because it allows me, in conjunction with containers, to
build up a single managable pool for a number of local host systems while
prototyping real storage requirements. I'd love the ability to migrate a test
container to new hardware and replicate the data with zfs send/receive, then be
able to resize my local pool. For production migration I already use 1 pool per
container then export/import to pool into other systems on the SAN for
redundancy/upgrades. Another thing that would be hot would be the ability to
swap in and out a slower/differently sized set of drives into a pool for a
faster set of drives, without incurring downtime. I ran into a situation where
I wanted to migrate data out to more spindles on smaller drives, which I had
available. Had remove been available I could have simply added the new smaller
drive mirrors into the pool then removed the larger drives and freed up their
use with no downtime. As your dataset gets larger in production, this becomes
more of a desirable feature.
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
