ger...@free wrote: > Evan Layton wrote: >> Hi Gerard, >> >> I'm sorry I missed that you had used zoneadm to clone the zones. It >> appears that what you're running into is >> http://bugs.opensolaris.org/view_bug.do?bug_id=6662360 >> >> What's happening is when you clone the zone it does a ZFS clone of the >> original zone. Because to now have this dependent clone it can't >> destroy the parent. What needs to happen is the clone needs to be >> promoted and once that's done you can then uninstall the first zone. >> The work around is to promote the ZFS dataset of the clone. >> >> For example: >> zoneadm -z zone2 clone zone1 >> zfs promote rpool/zones/zone2/ROOT/zbe > > can i make the assumption that i need to add the following command every > time i create a new clone: > zfs promote rpool/zones/zone2/ROOT/zbe > ?
Not really this just shifts which clone has ben promoted and shifts the problem to what was the clone. However doing this when destroying the clone (uninstalling a zone) so that what is being removed no longer has any dependents would get you around the problem until this gets fixed. -evan > > at least until the bug is solved? > > > > thanks, > > gerard _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
