This morning's "zoneadm -z search-1 attach -F" and boot tripped over a funky mount:
[Wednesday, August 8, 2012 10:56:46 AM EDT] Mounting rpool/var/zones/search-1/rpool/export at /tmp/tmp.zxa40u/export with ZFS temporary mount [Wednesday, August 8, 2012 10:56:46 AM EDT] Mounting rpool/var/zones/search-1/rpool/export/home at /tmp/tmp.zxa40u/export/home with ZFS temporary mount cannot unmount '/tmp/tmp.zxa40u/export/home': Device busy cannot unmount '/tmp/tmp.zxa40u/export': Device busy rmdir: directory "/tmp/tmp.zxa40u": Directory not empty [Wednesday, August 8, 2012 10:56:47 AM EDT] Manual migration of export required. Potential conflicts in /var/opt/zones/search-1/root/export and rpool/var/zones/search-1/rpool/export. [Wednesday, August 8, 2012 10:56:47 AM EDT] Zone BE root dataset: rpool/var/zones/search-1/rpool/ROOT/solaris-4 [Wednesday, August 8, 2012 10:56:47 AM EDT] Cache: Using /var/pkg/publisher. Haven't seen this race condition in several months of daily zone detach/attach's. My other zones came up cleanly. I'm running Solaris 11 SRU 8.5. The work-around was to halt the zone, detach, zfs umount rpool/var/zones/search-1/rpool/export/home and rpool/var/zones/search-1/rpool/export, attach and boot. Where in the zone machinery does the code set the zone mountpoints to global's TMPDIR? John groenv...@acm.org _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
