Re: [OmniOS-discuss] Understanding OmniOS disk IO timeouts and options to control them

one more thing… > On Jan 4, 2017, at 10:29 AM, Richard Elling > wrote: > >> >> On Jan 4, 2017, at 10:04 AM, Chris Siebenmann wrote: >> >> We recently had a server reboot due to the ZFS vdev_deadman/spa_deadman >> timeout timer

Re: [OmniOS-discuss] Understanding OmniOS disk IO timeouts and options to control them

> On Jan 4, 2017, at 10:04 AM, Chris Siebenmann wrote: > > We recently had a server reboot due to the ZFS vdev_deadman/spa_deadman > timeout timer activating and panicing the system. If you haven't heard > of this timer before, that's not surprising; triggering it requires

Re: [OmniOS-discuss] Understanding OmniOS disk IO timeouts and options to control them

On Wed, Jan 4, 2017 at 1:04 PM, Chris Siebenmann wrote: > (I have a crash dump from this panic, so I can in theory use mdb > to look through it to see just what level an IO appears stuck at > if I know what to look for and how.) Hi Chris, I recently blogged about digging

[OmniOS-discuss] Understanding OmniOS disk IO timeouts and options to control them

We recently had a server reboot due to the ZFS vdev_deadman/spa_deadman timeout timer activating and panicing the system. If you haven't heard of this timer before, that's not surprising; triggering it requires an IO to a vdev to take more than 1000 seconds (by default; it's controlled by the