tag:blogger.com,1999:blog-9963485.post1171191103630230399..comments2024-02-12T12:52:03.999+01:00Comments on Robert Milkowski's blog: zpool splitmilekhttp://www.blogger.com/profile/13649951503953000496noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-9963485.post-11429168506370523812010-10-26T16:42:58.822+02:002010-10-26T16:42:58.822+02:00Thanks...Very useful & informativeThanks...Very useful & informativeUnknownhttps://www.blogger.com/profile/09299423289818014597noreply@blogger.comtag:blogger.com,1999:blog-9963485.post-72684904115001859222010-01-06T17:00:14.862+01:002010-01-06T17:00:14.862+01:00man zfs:
send/receive in a pipe
do you want a snap...man zfs:<br />send/receive in a pipe<br />do you want a snapshot or a clone ?<br />RegardsAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-9963485.post-43970403445319633792010-01-05T18:33:58.143+01:002010-01-05T18:33:58.143+01:00I'd already stated that my method can be impor...I'd already stated that my method can be imported on the host system.<br /><br />As for the other points: With some scripting, it would be pretty easy to export ALL the datasets at once too (and /without/ having to hardcode the dataset names into the script!) plus, depending on how clever you are with your script, you shouldn't need double the disk space.<br /><br />I don't mean to state that "split" would be a useless tool - just that the previous method seems a slightly dangerous work-around for performing something that could already be done safely with standard ZFS functionality.Laurencenoreply@blogger.comtag:blogger.com,1999:blog-9963485.post-87275198147419574212010-01-05T17:45:16.204+01:002010-01-05T17:45:16.204+01:00Yes, that'll get you a copy of that dataset. ...Yes, that'll get you a copy of that dataset. However, using the split command:<br /><br /><b># zpool split tank newdisk</b><br /><br />Is all you need, and gets you ALL the datasets at once. It also doesn't require you to have double the space on newdisk (the space used to store the "split.save" zfs stream + the extracted data). It also relies on the mirroring code within the kernel to perform the copy when "zpool attach" is run, rather than copying it between userspace and kernel space twice, which would be a performance killer.<br /><br />And it is possible to import it on the same host, simply by using the zpool import command.markmhttps://www.blogger.com/profile/00704606393319344033noreply@blogger.comtag:blogger.com,1999:blog-9963485.post-90258933168609546482010-01-05T14:32:44.785+01:002010-01-05T14:32:44.785+01:00I should have added, my method also allows you to ...I should have added, my method also allows you to have the same two splits live on the same host (unlike the mirror method)Laurencenoreply@blogger.comtag:blogger.com,1999:blog-9963485.post-48696462364228178472010-01-05T14:30:27.688+01:002010-01-05T14:30:27.688+01:00The same could be achieved with the snapshot tools...The same could be achieved with the snapshot tools:<br /><br />create a blank zpool on the new disk (/newdisk)<br /><b><br /># zfs snapshot tank/home@split<br /># zfs send tank/home@split > /newdisk/split.save<br /># zfs receive /newdisk/home < /newdisk/split.save<br /># export zpool newdisk<br /></b><br /><br />then you can remove your disk and insert into whichever machine you want and re-import it.<br /><br />(I'm pretty sure you can use the same tools for root zpools and without creating a new zpool on the new disk, but I don't have access to my test zone so working purely from memory).Laurencenoreply@blogger.com