Date: Mon, 19 Jul 2010 08:41:40 -0400 From: Mike Tancsa <mike@sentex.net> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: deadlock or bad disk ? RELENG_8 Message-ID: <201007191241.o6JCfcq5049355@lava.sentex.ca> In-Reply-To: <20100719035844.GA93487@icarus.home.lan> References: <201007182108.o6IL88eG043887@lava.sentex.ca> <20100718211415.GA84127@icarus.home.lan> <201007182142.o6ILgDQW044046@lava.sentex.ca> <20100719023419.GA91006@icarus.home.lan> <201007190301.o6J31Hs1045607@lava.sentex.ca> <20100719033424.GA92607@icarus.home.lan> <20100719035844.GA93487@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:58 PM 7/18/2010, Jeremy Chadwick wrote:
>So I believe this indicates the message only gets printed during swapin,
>not swapout. Meaning it's happening during an I/O read from da0.
Yes, and from my existing ssh sessions, it would _seem_ no disk IO
was completing. ie I tried a killall -9 watchdogd which would need
to load killall from the disk, read whatever its linked against.
However, after hitting enter it was just blocking on trying to read.
So I would describe it as if the entire system was waiting from that
"swapper Indefinite wait" to finish, or I could not read anything
from drives associated with that controller.
>So what's hz? Well, I want to assume it's kern.hz, which defaults to
>1000. 1000*20 = 20000, so the timeout would be 20000/1000 = 20 seconds.
>That's a pretty long time to be waiting for an I/O read to return.
I think the messages were printing to the serial console faster than
that, but I could be wrong. If it happens again, I will time it
---Mike
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201007191241.o6JCfcq5049355>