Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Jan 2004 10:36:10 -0500
From:      "Robin P. Blanchard" <robin.blanchard@gactr.uga.edu>
To:        "Andre Guibert de Bruet" <andy@siliconlandmark.com>, "Ken Smith" <kensmith@cse.Buffalo.EDU>, "Kris Kennaway" <kris@obsecurity.org>, <current@freebsd.org>
Subject:   RE: Processes blocked on ufs or getblk
Message-ID:  <EE3D3FBAFFCAED448C21C398FDAD91AC0108E4@EBE1.gc.nat>

next in thread | raw e-mail | index | archive | help

> I'm reviving this thread as I have more information that=20
> might help track this problem down. The offending process in=20
> this case is gqview but it could have been 'find /' or any=20
> other process running when there's high system load (such as daylies).
>=20
> >From the emails that I've gotten it appears that this bug=20
> affects users
> that are using either ccd or hardware raid (amr driver in my=20
> case). I've attached the output of a ddb ps and a 'show lockednods'.
>=20
> Every time the getblk hang rears it's ugly head, I've seen
> "amr0: bad slot x completed" (where x is an integer between 0=20
> to 4) printed on the serial console.
>=20
> This makes me think that there's a failure mode or special=20
> state that isn't being checked with the amr driver. Perusing=20
> the code shows that the bad slot message is a result of a=20
> NULL busy command. I'm no storage driver and my VFS knowledge=20
> is somewhat limited. Anyone out there want to have a look at=20
> this? I'm willing to try out any patches on this system.


As seen previously on this list, I'm also seeing processes getting stuck =
in
in "getblk" state. I'm seeing this on a dell 2650 (smp enabled, acpi =
enabled,
aac filesystem). I'm also more than willing to try out any patches =
anyone may
cook up.=20

---------------------------------------
Robin P. Blanchard
Systems Integration Specialist
Georgia Center for Continuing Education
fon: 706.542.2404 < > fax: 706.542.6546
---------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EE3D3FBAFFCAED448C21C398FDAD91AC0108E4>