This content has been marked as final. Show 7 replies
two pieces of information are needed:
1. what does the /var/adm/messages file of the zone tell you?
2. how is the zone setup? Where and how is the root filesystem setup and what filesystems are lofi mounted from the global zone?
These infos should give us a clue.
The /var/adm/messages doesn't show anything particular about the zones getting hung.
The root filesystem is a ufs FS.
If you encounter the issue again in future, please get a system crash dump by panicing the global zone. This will allow us (support) to review the crash dump and understand why the zone failed to shut down. It will have been waiting on a resource and without the dump there's simply no way to know what or why.1 person found this helpful
IIRC we recently (with the past month) did a putback of a bug (which I can't find the ID of right now) whereby if a zone doesn't hang on the way down we'll fork a new instance of the zone and leave the old refs in their hung state. So it's worth ensuring that you're running the latest Patchset.
I am wondering whether the non-global zone is an NFS client and has some hanging NFS mounts.
Also, you did not tell us whether this is a full or sparse root zone.
The server is running in
# uname -a
SunOS myriad 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V440
I'll ensure that if the same issue comes up, there is a dump taken when we reboot it.
Thanks for the inputs.
No.. These zones are not NFS client and no NFS mounted in the zone.
Its a whole root zone.
Thanks for the inputs given.