> On Apr 3, 2017, at 3:38 PM, Bob Friesenhahn
> wrote:
>
> It does not seem that you obtained the same initial error message ("failed to
> open console master: Device busy") that I always do.
When it fails, I *DO* see this.
Apr 3 15:22:16 bloody
> On Apr 3, 2017, at 3:18 PM, Dan McDonald wrote:
>
> AND THINGS GET WEIRDER.
>
> After the failure I documented earlier, I went off to do something else.
> When I came back, the zsched process was gone, and the zone appeared to be
> properly shut down.
>
> So I booted
> On Apr 3, 2017, at 2:59 PM, Dan McDonald wrote:
>
> Okay. I will be diving into this now to see WTF happened. I'm sorry for not
> paying closer attention to this sooner.
AND THINGS GET WEIRDER.
After the failure I documented earlier, I went off to do something else.
> On Apr 3, 2017, at 2:11 PM, Bob Friesenhahn
> wrote:
>
> The problem is definintely with zone 'shutdown'. I have never seen it happen
> with 'reboot' or 'halt'.
Which does go through the inittab things.
I've found something. I can reproduce this on bloody
On Mon, 3 Apr 2017, Dan McDonald wrote:
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.
I've
> On Apr 3, 2017, at 1:40 PM, Bob Friesenhahn
> wrote:
>
> The common theme is always the first message "failed to open console master:
> Device busy". The failure to unmount filesystems is new to me.
That could be something from the LX code, but I'm not seeing
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
> On Apr 2, 2017, at 7:07 PM, Bob Friesenhahn
> wrote:
>
> Previously I reported a problem (in the 040 timeframe) in that zones are
> hanging when being shut down. Problems continue on that system. Today I am
> seeing the same issue with a different OmniOS