Hi, after going deep into my cloning problem, I discovered what happened. I created the dstzone by exporting the srczone config, changing the dataset name, and creating the new dstzone with zonecfg. Then cloned with "zoneadm -z dstzone clone srczone". Usuallly this will create a new "dstzone", "dstzone/ROOT" and "dstzone/ROOT/zbe" clone of the original. For some reason the command tried to snapshot and create a second zbe (zbe-1) on the srczone, then probably try to install/clone over the same srczone, failing and putting my srczone into incomplete state. I could revert to a correct state by removing the "still-not-cloned" but configured clone (dstzone), use zpool history to check the last commands of snapshot and clone, then destroy the zbe-1 clone and the associated snapshot. Then I had to manually edit /etc/zone/index and change "incomplete" into "installed". Finally used zoneadm to set the srczone to ready, and then safely boot srczone. Now. What was the cause of the failure? The srczone had datasets of the global zone assigned with "add dataset". I needed this dataset in the cloned zone, while the srczone was halted, to make tests. Because this dataset was present in two zones, the clone command did the above problem! I had to remove the dataset from the srczone before cloning, and the clone worked as always correctly :) Is this a bug or what? Gabriele.
------------------------------------------- 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
