You can look at the following thread where I had a similar problem with a zone stuck in a shutting down state:
http://opensolaris.org/jive/thread.jspa?threadID=101438&tstart=30 The other thing to look for is processing that might be accessing the ngz from the gz using fuser. You can also use pwdx /proc/* | grep slabzone1to find process. If you find any you can see what they are doing and kill them, then try shutting down the zone again. Otherwise I haven't found a way to kill the short of rebooting the box. As an aside, I was under the impression that it was not advisable to access ngz filesystems from the gz. A quick search only seems to point to the gz possibly doing something nefarious to the ngz but I can't find any technical reason it shouldn't be done. On Fri, Jul 10, 2009 at 10:58 AM, <ajmai...@mchsi.com> wrote: > I needed to share out a non-global zones folder via nfs so I did it from > the global zone like so: > > # share /slabzone1/zonepath/root/home > > Later I rebooted the zone: > # zoneadm -z slabzone1 reboot > > The reboot command hung and the zone became stuck in the "down" status. I > assume this is because of the nfs share, I tried unsharing it, but that > didn't help: > > # unshare /slabzone1/zonepath/root/home > nfs unshare: /slabzone1/zonepath/root/home: not shared > > My attempts to get the zone to transistion to "installed" state have all > failed. I assume this is a known issue, is there anyway to recover without > a reboot? > > Thanks, > > Alex > > _______________________________________________ > zones-discuss mailing list > zones-discuss@opensolaris.org >
_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
