Re: [zones-discuss] /var/run/zones not cleaned up ?
Feature. It is the F_WRLCK operation which takes the lock. I suppose this avoids having to deal with stale lock files from dead zoneadm's. Similar for the door. The door file is he who fattaches, not he who creates the door file. Saying that, I don't see a problem with the unlock/fdetach operations removing these files, as long at they are truely done, and it ok for a new lock/door to be created. -Steve On Thu, Dec 10, 2009 at 04:37:17PM +0100, Frank Batschulat (Home) wrote: > is it to be expected that after no zoneadm/zoneadmd is running > anymore, /var/run/zones still contains the corresponding lock files ? > > (also I looked at the current threadlist of my system and no zone releated > kernel threads are running anymore) > > osoldev.root./var/run/zones.=> zoneadm list -cp > 0:global:running:/::ipkg:shared > -:zone2:configured:/tank/zones/zone2::ipkg:shared > osoldev.root./var/run/zones.=> ps -eafd|grep zone > root 2961 2734 0 16:35:06 pts/2 0:00 grep zone > osoldev.root./var/run/zones.=> ls -la > total 16 > drwx-- 2 root root 335 Dec 10 12:23 . > drwxr-xr-x 11 root sys 2423 Dec 10 12:21 .. > -rw-r--r-- 1 root root 0 Dec 10 12:23 index.lock > -rw--- 1 root root 0 Dec 10 12:21 zone1.zoneadm.lock > -rw--- 1 root root 0 Dec 10 12:21 zone1.zoneadmd_door > > this was after a zone boot/zone halt/zone uninstall/zone delete cycle. > > bug, feature ? > > --- > frankB > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
On 12/ 8/09 11:50 AM, xx wrote: when updating from 126 to 128, one zone would attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach -U Log File: /var/tmp/ldap.attach_log.9hay7p Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.111:20090514T145840Z Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows DOWNLOAD PKGS FILESXFER (MB) Completed 112/112 10121/10121 126.3/126.3 PHASEACTIONS Removal Phase 4727/4727 Install Phase10622/10622 Update Phase 5073/5073 Updating non-global zone: (Stage 2). Output follows No updates necessary for this image. ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ zoneadm list -v ID NAME STATUS PATH BRANDIP 0 global running/ ipkg shared init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldap attach Log File: /var/tmp/ldap.attach_log.8ea4wq Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Evaluation: Packages in ldap are in sync with global zone. Attach complete. and one won't attach: init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach -U Log File: /var/tmp/ldapclient.attach_log.E6aOvx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Qt WARNING: QClipboard: Unknown SelectionClear event received Publisher Check: Zone preferred publisher does not contain ent...@0.5.11,5.11-0.128:20091125T051747Z. Publisher Reset: Copying preferred publisher from global zone. Cache: Using /var/pkg/download. Updating non-global zone: (Stage 1). Output follows Creating Plan ERROR: Could not update attaching zone init...@dogpatch:~/.VirtualBox/HardDisks$ pfexec zoneadm -z ldapclient attach Log File: /var/tmp/ldapclient.attach_log.aeayVx Attaching... Global zone version: ent...@0.5.11,5.11-0.128:20091125T051747Z Non-Global zone version: ent...@0.5.11,5.11-0.126:20091022T214456Z Evaluation: ldapclient is downrev of the global zone. ERROR: Zone is downrev of global zone. Specify -u to update it. how do you go about figuring out why it won't update? i tried both "-U" and "-u". You might be hitting bug 13190 (http://defect.opensolaris.org/bz/show_bug.cgi?id=13190). Try Jerry Jelinek's workaround as described in the bug report. (NOTE: The attach script that he mentions is /usr/lib/brand/ipkg/attach) Make sure that the publishers used by your zones exist and can be reached from the global zone. Hope that helps, Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] /var/run/zones not cleaned up ?
is it to be expected that after no zoneadm/zoneadmd is running anymore, /var/run/zones still contains the corresponding lock files ? (also I looked at the current threadlist of my system and no zone releated kernel threads are running anymore) osoldev.root./var/run/zones.=> zoneadm list -cp 0:global:running:/::ipkg:shared -:zone2:configured:/tank/zones/zone2::ipkg:shared osoldev.root./var/run/zones.=> ps -eafd|grep zone root 2961 2734 0 16:35:06 pts/2 0:00 grep zone osoldev.root./var/run/zones.=> ls -la total 16 drwx-- 2 root root 335 Dec 10 12:23 . drwxr-xr-x 11 root sys 2423 Dec 10 12:21 .. -rw-r--r-- 1 root root 0 Dec 10 12:23 index.lock -rw--- 1 root root 0 Dec 10 12:21 zone1.zoneadm.lock -rw--- 1 root root 0 Dec 10 12:21 zone1.zoneadmd_door this was after a zone boot/zone halt/zone uninstall/zone delete cycle. bug, feature ? --- frankB ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Solaris10-Branded Zones Webrev: CR 6882732
On Wed, 09 Dec 2009 23:54:05 +0100, Jordan Vaughan wrote: > I need someone to review my fix for > > 6882732 unpacking archive with extended file attributes reports errors > > The webrev is accessible via > > http://cr.opensolaris.org/~flippedb/onnv-s10c looks good to me. cheers --- frankB ___ zones-discuss mailing list zones-discuss@opensolaris.org
