# [OmniOS-discuss] Continuing hung-zone problems

Bob Friesenhahn bfriesen at simple.dallas.tx.us
Mon Apr 3 17:40:41 UTC 2017

- Previous message: [OmniOS-discuss] Continuing hung-zone problems
- Next message: [OmniOS-discuss] Continuing hung-zone problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Mon, 3 Apr 2017, Dan McDonald wrote:
    >
    > If you have a shell available, you should inspect the available processes to see what all is stuck in where.

    I will try to find some time for such activities.

    >> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] failed to open console master: Device busy
    >> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] WARNING: could not open master side of zone console for swdev to release slave handle: Device busy
    >> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] WARNING: console /devices//pseudo/zconsnex at 1/zcons at 0 found, but it could not be removed.: I/O error
    >> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] unable to unmount '/zones/swdev/root/proc'
    >> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] unable to unmount file systems in zone
    >> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] unable to destroy zone
    >> Apr  2 17:51:53 velma svc.startd[10]: [ID 122153 daemon.warning] svc:/system/zones:default: Method or service exit timed out.  Killing contract 169.
    >> Apr  2 17:51:53 velma svc.startd[10]: [ID 636263 daemon.warning] svc:/system/zones:default: Method "/lib/svc/method/svc-zones stop" failed due to signal KILL.
    >
    > You did say you were using that zone as an NFS client.  Perhaps one of the processes wasn't really done accessing a remote filesystem?  I noticed the unmountable filesystem is procfs for that zone.  I can't tell you why that's interesting off the top of my head, that IS interesting to know, however.

    The zone uses the automounter and NFS mounts would not have been made
    due to the zone simply having been booted for a minute or two.

    All of my zones (some of which do not use NFS and have almost every
    network service disabled) on my two OmniOS systems are equally plagued
    with this issue.  I know that I am not alone since others have
    reported that this is happening to them.

    The zone configuration seems quite simple.  Is there something about
    it which might cause an issue?

    The common theme is always the first message "failed to open console
    master: Device busy".  The failure to unmount filesystems is new to
    me.

    Bob
    --
    Bob Friesenhahn
    bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
    GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

- Previous message: [OmniOS-discuss] Continuing hung-zone problems
- Next message: [OmniOS-discuss] Continuing hung-zone problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list