Jonathan, On Tue, Mar 04, 2008 at 12:37:33AM -0800, Jonathan Loran wrote: > I'm 'not sure I follow how this would work.
The keyword here is thin provisioning. The sparse zvol only uses as much space as the actual data needs. So, if you use a sparse zvol, you may mirror to a smaller "disk", iff you use as much space as is physically available to the sparse zvol. > I do have tons of space on > the old array. It's only 15% utilized, hence my original comment. How > does my data get into the /test/old zvol (zpool foo)? What would I end > up with. There's no zvol on foo. After detaching /test/old, you may reconfigure your old array. At that point, foo is on a zvol on the pool bar. In what way to get the data over depends on how your reconfiguration of the old array impacts the pool and vdev size. If it gets smaller, you cannot attach it to the pool where your data currently resides and have to go the send|receive route... Putting the zpool on a zvol permanently might not be something you want as this creates some overhead, I can't quantisize, and you mentioned some performance issues you're already experiencing. > This seems a bit like black magic. Maybe that's what I need, > eh? Feel the magic at http://www.cuddletech.com/blog/pivot/entry.php?id=729 Greetings, Patrick _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
