I have had the same problem with two zones and using the following two steps
I was able to get one of the zones to shut down and the other one I wasn't.

First, check for hung nfs mounts for the ngz from the gz.  mount | grep
www2.  If you see any umount them from the gz.

Next, check for any processes that might be accessing files in the ngz. From
the gz you can do something like:

#  pwdx /proc/* | grep zone1
17459:  /export/zone/zone1/root
17731:  /export/zone/zone1/root/tmp
18022:  /export/zone/zone1/root/tmp

# ps -ef | egrep "18022|17731"
    root 18022 17731   0 13:15:33 pts/2       0:00 sleep 500000
    root 18064 17745   0 13:17:40 pts/1       0:00 egrep 18022|17731
    root 17731 17727   0 13:14:18 pts/2       0:00 sh


If you find any processes you can try and kill them.


After each step try and halt the zone and see if it comes down.

If neither of these work the only solution I've heard of is rebooting the
host.

On Sun, Jun 21, 2009 at 6:25 AM, solarg <sol...@laposte.net> wrote:

> hello all,
> after trying to reboot a zone, it still hang:
> he...@antigone:~# zoneadm -z www2 reboot;zlogin -C www2
>
> on other termial, i try to kill the process:
> he...@antigone:~# ps -ef|grep www2
>    root 16432     1   0   Mar 18 ?           0:03 zoneadmd -z www2
>    root 18864 18860   0 12:18:14 pts/5       0:00 grep www2
>    root 18809 11676   0 12:09:53 pts/3       0:00 zoneadm -z www2 reboot
> he...@antigone:~# kill -9 16432
>
> and:
> he...@antigone:~# zoneadm -z www2 reboot;zlogin -C www2
> door_call failed: Interrupted system call
> zone 'www2': WARNING: zone is in state 'down', but zoneadmd does not appear
> to be available; restarted zoneadmd to recover.
> [Connected to zone 'www2' console]
> ~^D
>
> he...@global:~# zoneadm list -cv
>  ID NAME             STATUS     PATH                           BRAND
>  73 www2             down       /zones/www2                    ipkg shared
>
> i also have:
> he...@antigone:~# mdb -k
> > ::walk zone | ::print zone_t zone_name zone_ref
> ...
> zone_name = 0xffffff044b049c80 "www2"
> zone_ref = 0x2
>
> a precedent thread said:
> "If the refcount is greater than 0x1, it could be:
>        6272846 User orders zone death; NFS client thumbs nose
> "
>
> he...@antigone:~# ps -ef|grep www2
>    root 19091 18860   0 13:19:32 pts/5       0:00 zoneadm -z www2 halt
>    root 19093     1   0 13:19:32 ?           0:00 zoneadmd -z www2
>    root 19113 11676   0 13:24:30 pts/3       0:00 grep www2
> he...@antigone:~# truss -p 19093
> /4:     door_return(0x00000000, 0, 0x00000000, 0xFE4F0E00, 1007360)
> (sleeping...)
> /3:     zone_destroy(73)                (sleeping...)
> /1:     pollsys(0x08046AD0, 4, 0x00000000, 0x00000000) (sleeping...)
> /2:     door_unref()                    (sleeping...)
> he...@antigone:~# truss -p 19091
> door_call(6, 0x08047590)        (sleeping...)
>
>
> Any idea?
>
> thanks for help,
>
> gerard
> _______________________________________________
> zones-discuss mailing list
> zones-discuss@opensolaris.org
>
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to