On Tue, 23 Feb 2010 10:27:21 +0100, Frank Batschulat (Home) <frank.batschu...@sun.com> wrote:
> however contrary to this description and your case, in my tests this just > renames > the zfs mount point property and does notthing else, even when the move would > cross > file system boundaries: > > osoldev.root./export/home/batschul.=> zoneadm list -cp > 0:global:running:/::ipkg:shared > -:zone1:installed:/tank/zones/zone1:caa7e784-dab0-6f77-e202-8cf135714809:ipkg:shared > > osoldev.root./export/home/batschul.=> zfs list -t all > NAME USED AVAIL REFER > MOUNTPOINT > tank/zones 996M 151G 38K > /tank/zones > tank/zones/zone1 996M 151G 36K > /tank/zones/zone1 > tank/zones/zone1/ROOT 996M 151G 31.5K legacy > tank/zones/zone1/ROOT/zbe 996M 151G 996M legacy [...] > 2) moving to different zfs dataset and different pool, rpool/export/home > > osoldev.root./export/home/batschul.=> zoneadm -z zone1 move /export/home/test2 > > osoldev.root./export/home/batschul.=> zoneadm list -cp > 0:global:running:/::ipkg:shared > -:zone1:installed:/export/home/test2:caa7e784-dab0-6f77-e202-8cf135714809:ipkg:shared > > osoldev.root./export/home/batschul.=> zfs list -t all > NAME USED AVAIL REFER > MOUNTPOINT > tank/zones 996M 151G 36.5K > /tank/zones > tank/zones/zone1 996M 151G 36K > /export/home/test2 > tank/zones/zone1/ROOT 996M 151G 31.5K legacy > tank/zones/zone1/ROOT/zbe 996M 151G 996M legacy > > so there's no "move" in the sense of move happening in case 2) this seems > wrong to me. [...] > but I can not find anything existing for suspect 2) and the missing "move" > action here as not only do we cross file system boundaries but we do even move > over to a different pool! > > so either we'd need to enhance the scope of 6918505 or a new bug > ought to be filed for case 2) yes, this is a new, different bug in zoneadm.c:move_func() - I filed for this: 6929224 zoneadm move does not move across zfs file systems anylonger --- frankB _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
