I guess my wording was a little confusing. What I meant by nfs mounts in
the ngz from the gz is that since you can't log into the zone you need to
check for hung nfs mounts from the global zone. The nfs mounts that we have
had hung were from filers.
Derek
On Sun, Jun 21, 2009 at 3:05 PM, Craig
thanks for all replies.
Unfortunately, i was forced to reboot the machine without understanding
what was happening. And now, it's ok
gerard
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Steve,
Thanks for this information.
I ran through the commands and this is what I see.
::kmem_cache ! grep rnode
a6438008 rnode_cache 0200 00 65670506
a643c008 rnode4_cache 0200 00 9680
When I run the following:
The zone is in a shutting_down state.
The mdb command for this zone returns 0x1a, greater then 1.
zone_name = 0xfe86c83d61c0 zonetest-new
zone_ref = 0x1a
This is new to me, what is the refcount counting? What should this value be
for the zone to shutdown?
There is a zoneadmd processes
I already tried killing the zoneadmd process and issuing the halt and all
it does is start back up the zoneadmd process and hang.* I can't force a
crashdump on the system since I can't take the box down.
Bug 6272846 makes reference to nfs version 3, (which is the version we are
I don't believe that I can see the comments since they are not public.
Is that something you can pass along?
On Wed, May 6, 2009 at 5:27 PM, Steve Lawrence stephen.lawre...@sun.comwrote:
I already tried killing the zoneadmd process and issuing the halt and
all
it does is start back
Related comments from bug below (X'ed out some paths):
The zone in question clearly has too many references
030004a09680::print zone_t zone_ref
zone_ref = 0t11
Ten too many, to be precise. So what's holding onto the zone? Well the rnode
cache has 5 entries
::kmem_cache ! grep rnode
Just follow up on the progress and resolution to my stuck zones problem. I
had two zones stuck in the shutting_down state.
Based on initial feedback I looked for nfs mounts in /etc/mnttab in the gz
that were mounted in the ngz. There were a couple and umount'ed them. Then I
was able to find two
It's possible that it could be nfs mount related since the zone did have nfs
mounted fs's but they should have been umounted prior to shutting down the
zone. In any event I can no longer get into the zone to checkusing zlogin
and zlogin -C.
I tried Bryan's suggestion on looking for processes
Derek McEachern wrote:
It's possible that it could be nfs mount related since the zone did
have nfs mounted fs's but they should have been umounted prior to
shutting down the zone. In any event I can no longer get into the
zone to checkusing zlogin and zlogin -C.
I tried Bryan's suggestion
If its hung nfs mount you should be able to see it still mounted in
the /etc/mntab file in the global zone: grep nfs /etc/mntab. It will be
mounted under the zonepath. You should then be able to do a umount
-f /path-to-nfsmnt from the global zone and if you're really lucky the
zone will finish
There were a bunch of nfs mounts listed in the /etc/mntab of the global
zone. I was able to umount them but zone is still hung up.
I tried killing the zoneadmd process and ran zoneadm halt again and it
started the zoneadmd back up but it didn't do anything.
Thanks to everyone for their
12 matches
Mail list logo
