On 11/19/12 14:19, Ian Collins wrote:
After a recent system panic, the zones service failed to start due to
the first zone failing to boot. The boot fails with
ERROR: could not open master side of zone console for wiki to acquire
slave handle: Device busy
I tried detaching and reattaching the zone but this didn't change anything.
Can this be fixed by removing the /dev/zcons/wiki symlinks or the
underlying pseudo devices?
When are the pseudo devices created?
When the zone boots.
It turns out there are two zones attempting to use the same console devices:
s -l /dev/zcons/sword/
total 0
lrwxrwxrwx 1 root root 0 Nov 11 10:46 masterconsole ->
../../../devices/pseudo/zconsnex@1/zcons@1:masterconsole
lrwxrwxrwx 1 root root 0 Nov 11 10:46 zoneconsole ->
../../../devices/pseudo/zconsnex@1/zcons@1:zoneconsole
ls -l /dev/zcons/wiki
total 0
lrwxrwxrwx 1 root root 0 Nov 20 11:47 masterconsole ->
../../../devices/pseudo/zconsnex@1/zcons@1:masterconsole
lrwxrwxrwx 1 root root 0 Nov 20 11:47 zoneconsole ->
../../../devices/pseudo/zconsnex@1/zcons@1:zoneconsole
Which explains why the devices are busy!
Even after detaching, deleting, recreating and attaching, the zone still
attempts to use the same devices.
In the end I resorted to detaching, deleting, recreating with a new name
and attaching.
PITA.
--
Ian.
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
