kern/179932: [ciss] ciss i/o stall problem with HP Bl Gen8 (and HP Bl Gen7 + Storage Blade)

Fri Jul 5 14:20:01 UTC 2013

The following reply was made to PR kern/179932; it has been noted by GNATS.

From: Markus Gebert <markus.gebert at hostpoint.ch>
To: Steven Hartland <killing at multiplay.co.uk>
Cc: freebsd-scsi at FreeBSD.org,
 "bug-followup at FreeBSD.org" <bug-followup at FreeBSD.org>
Subject: Re: kern/179932: [ciss] ciss i/o stall problem with HP Bl Gen8 (and HP Bl Gen7 + Storage Blade)
Date: Fri, 5 Jul 2013 16:14:26 +0200

 --Apple-Mail=_9D4196B5-B411-44BB-BDE1-8695E2E76451
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain;
 	charset=windows-1252

 Hey Steven

 Thanks for your input.

 On 05.07.2013, at 15:43, Steven Hartland <killing at 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

 --Apple-Mail=_9D4196B5-B411-44BB-BDE1-8695E2E76451
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/html;
 	charset=windows-1252

 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
 charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
 -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
 "><div>Hey Steven</div><div><br></div><div>Thanks for your =
 input.</div><br><div><div>On 05.07.2013, at 15:43, Steven Hartland =
 <<a =
 href=3D"mailto:killing at multiplay.co.uk">killing at multiplay.co.uk</a>> =
 wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
 type=3D"cite"><span style=3D"font-family: Helvetica; font-size: medium; =
 font-style: normal; font-variant: normal; font-weight: normal; =
 letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
 -webkit-auto; text-indent: 0px; text-transform: none; white-space: =
 normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
 -webkit-text-stroke-width: 0px; display: inline !important; float: none; =
 ">Might also want to get the output from "show sleepchain" for all =
 threads</span><br style=3D"font-family: Helvetica; font-size: medium; =
 font-style: normal; font-variant: normal; font-weight: normal; =
 letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
 -webkit-auto; text-indent: 0px; text-transform: none; white-space: =
 normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
 -webkit-text-stroke-width: 0px; "><span style=3D"font-family: Helvetica; =
 font-size: medium; font-style: normal; font-variant: normal; =
 font-weight: normal; letter-spacing: normal; line-height: normal; =
 orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
 none; white-space: normal; widows: 2; word-spacing: 0px; =
 -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: =
 inline !important; float: none; ">too as that will easily identify sleep =
 lock dead locks.</span><br style=3D"font-family: Helvetica; font-size: =
 medium; font-style: normal; font-variant: normal; font-weight: normal; =
 letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
 -webkit-auto; text-indent: 0px; text-transform: none; white-space: =
 normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
 -webkit-text-stroke-width: 0px; "></blockquote><div><br></div><div>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?</div><div><br></div><br><blockquote type=3D"cite"><span =
 style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
 font-variant: normal; font-weight: normal; letter-spacing: normal; =
 line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
 display: inline !important; float: none; ">Also whats the check_disk =
 process?</span></blockquote></div><br><div>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.</div><div><br></div><div><br></div><div>Markus</div><div><br></d=
 iv></body></html>=

 --Apple-Mail=_9D4196B5-B411-44BB-BDE1-8695E2E76451--