Date: Fri, 5 Jul 2013 16:14:26 +0200 From: Markus Gebert <markus.gebert@hostpoint.ch> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-scsi@FreeBSD.org, "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org> Subject: Re: kern/179932: [ciss] ciss i/o stall problem with HP Bl Gen8 (and HP Bl Gen7 + Storage Blade) Message-ID: <E1E02BBC-23BD-42C7-832D-3B3D606523B6@hostpoint.ch> In-Reply-To: <F9708744CDC74491A39BB8B21518C5B7@multiplay.co.uk> References: <201307051230.r65CU15d060678@freefall.freebsd.org> <F9708744CDC74491A39BB8B21518C5B7@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey Steven Thanks for your input. On 05.07.2013, at 15:43, Steven Hartland <killing@multiplay.co.uk> = wrote: > Might also want to get the output from "show sleepchain" for all = threads > too as that will easily identify sleep lock dead locks. Is there an easy way to do this for all threads with one command? The = first server that crashed had 800 threads=85 If not, we should probably = script this outside of ddb using thread ids from the alltrace output. Or = is there a subset of threads you're particularly interested in? > Also whats the check_disk process? This is Nagios' check_disk plugin we use to check the filesystem usage = on all mountpoints. It runs quite frequently, that's why multiple may be = get started until we notice and break into the debugger. Markus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1E02BBC-23BD-42C7-832D-3B3D606523B6>