You mean I could send the clone entirely without requiring the origin by omitting -R? Problem is, I had to send all clone fs structure: clone, clone/ROOT and clone/ROOT/zbe. Maybe I could have sent them one by one without -R? Gabriele. Da: Matthew Ahrens A: [email protected] Data: 22 gennaio 2013 2.23.51 CET Oggetto: Re: [discuss] zfs clones/origins On Mon, Jan 21, 2013 at 10:12 AM, Gabriele Bulfon [email protected] wrote: Actually, maybe the problem is right before: I ended up here while moving the cloned fs over another pool. Why send/recv complains of a missing clone at destination? Why not an option to send the fs together with the origin data? That's what I'm looking for at destination... I'm guessing you did: zfs send -R pool/clone@lastsnap This does assume that the clone's origin already exists on the receiving side (thus not "rehydrating" the clone). The cleanest solution would be to send the origin first (" zfs send `zfs get -H -o value origin pool/clone` | ... "). You could also send the clone independently: zfs send pool/clone@firstsnap | ... If you want all the snapshots of this clone, follow that up with: zfs send -I @snap pool/clone@lastsnap | ... --matt illumos-discuss | Archives | Modify Your Subscription
------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
