GLOBAL ZONE stuck in shutting_down after applying latest patch cluster

Question

Hi,
after installing the latest patch cluster, my zones on the system are not accessable
root@typhoon # zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global shutting_down / native shared
- typhoon-log installed /local/zone/typhoon-log native shared
- typhoon-ftp installed /local/zone/typhoon-ftp native shared
- typhoon-rndrepos installed /local/zone/typhoon-rndrepos native shared
- typhoon-drpreview installed /local/zone/typhoon-test native shared
- typhoon-ossec installed /local/zone/typhoon-ossec native shared
- typhoon-drjboss installed /local/zone/typhoon-drjboss native shared
- typhoon-webdata installed /datapool/web/zones/webdata native shared
- typhoon-webzone installed /datapool/web/zones/typhoon-webzone native shared
# uname -a
SunOS typhoon 5.10 Generic_139556-08 i86pc i386 i86pc
there is one service reporting in maintenane
# svcs -xv
svc:/system/filesystem/volfs:default (Volume Management filesystem)
State: maintenance since Wed Jul 15 20:04:07 2009
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/man -s 7FS volfs
See: /var/svc/log/system-filesystem-volfs:default.log
Impact: This service is not running.
I tried stopping and starting the vold, but without any effect
the / is on a zfs pool
# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
datapool 576G 105G 471G 18% ONLINE -
datapool2 148G 111G 37.0G 74% ONLINE -
rpool 120G 37.1G 82.9G 30% ONLINE -
root@typhoon # zpool status
pool: datapool
state: ONLINE
scrub: scrub completed after 0h31m with 0 errors on Thu Jul 16 02:31:53 2009
config:
NAME STATE READ WRITE CKSUM
datapool ONLINE 0 0 0
mirror ONLINE 0 0 0
c2d1s3 ONLINE 0 0 0
c1d1s3 ONLINE 0 0 0
errors: No known data errors
pool: datapool2
state: ONLINE
scrub: scrub completed after 1h53m with 0 errors on Wed Jul 15 23:53:06 2009
config:
NAME STATE READ WRITE CKSUM
datapool2 ONLINE 0 0 0
mirror ONLINE 0 0 0
c2d0s0 ONLINE 0 0 0
c1d0s3 ONLINE 0 0 0
errors: No known data errors
pool: rpool
state: ONLINE
scrub: scrub completed after 0h26m with 0 errors on Thu Jul 16 06:20:39 2009
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c1d1s0 ONLINE 0 0 0
c2d1s0 ONLINE 0 0 0
errors: No known data errors
root@typhoon #
# tail /var/svc/log/system-filesystem-volfs:default.log
[ Jul 16 08:03:11 Method "start" exited with status 0 ]
Thu Jul 16 08:03:11 2009 fatal: mounting of "/vol" failed
[ Jul 16 08:03:11 Stopping because all processes in service exited. ]
[ Jul 16 08:03:11 Executing stop method (:kill) ]
[ Jul 16 08:03:11 Executing start method ("/lib/svc/method/svc-volfs start") ]
[ Jul 16 08:03:11 Method "start" exited with status 0 ]
Thu Jul 16 08:03:11 2009 fatal: mounting of "/vol" failed
[ Jul 16 08:03:11 Stopping because all processes in service exited. ]
[ Jul 16 08:03:11 Executing stop method (:kill) ]
[ Jul 16 08:03:11 Restarting too quickly, changing state to maintenance ]
please advise, (this was on test run before implemention this patch cluster on the production server).
And I need to get a solution, to get my zone back running and then decide what to do with this patch cluster
thx
Edited by: Denis@SDN on Jul 16, 2009 1:06 AM

Answer 1

Sound familiar?
[http://opensolaris.org/jive/thread.jspa?threadID=105001&tstart=0]
This guy killed a process as workaround
[http://alittlestupid.com/2009/07/04/solaris-zone-stuck-in-shutting_down-state/]
We patched some SPARC systems recently and no issues though that's little consolation to you x86 admins.