Date: Thu, 1 Feb 2007 14:26:41 -0500 From: Kris Kennaway <kris@obsecurity.org> To: freebsd-stable@freebsd.org Subject: Re: Filesystem hang on 3ware 6.2 system Message-ID: <20070201192641.GA73043@xor.obsecurity.org> In-Reply-To: <20070201192454.GA63341@manor.msen.com> References: <20070131072435.GR63341@manor.msen.com> <20070131092816.GD56152@deviant.kiev.zoral.com.ua> <20070201192454.GA63341@manor.msen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 01, 2007 at 02:24:54PM -0500, Michael R. Wayne wrote: > On Wed, Jan 31, 2007 at 11:28:16AM +0200, Kostik Belousov wrote: > > On Wed, Jan 31, 2007 at 02:24:35AM -0500, Michael R. Wayne wrote: > > > We have a nubmer of similar machines that were initiallly formated > > > with 6.2 before it was released and have subsequently been upgraded > > > to 6.2-RELEASE with no issues. So, we upgraded a 6.1 box which has > > > been running fine as long as the nightly dumps do not use -L to > > > take snapshots. > > >=20 > > > Once it was upgraded to 6.2, we enabled -L on the nightly dumps and > > > it hung on the first try. So, I'm suspecting that 6.1 has left > > > SOMEthing on the filesystem which is corrupt. For the moment. we > > > have once again removed -L from the nightly dumps but, other than > > > a complete fsck, is there any other suggested action? > > >=20 > > > 6.2-RELEASE > > > twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x9= c00-0x9c0f mem 0xfc9ffc00-0xfc9ffc0f,0xfc000000-0xfc7fffff irq 20 at device= 1.0 on pci2 > > > twe0: [GIANT-LOCKED] > > > twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 > >=20 > > See kernel deadlock debugging chapter from the developer handbook for > > instructions on how to properly report deadlock. >=20 >=20 > I replied privately with no result, so I'll try the list again. >=20 > As I read the "kernel deadlock debugging chapter", I see that it > operates on core dumps. No, it (show lockedvnods, etc) operates from DDB; you need a serial or other console. Kris --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwj7xWry0BWjoQKURAgVbAKCgHUppLWFizOO+0XcXfMeaZJUruQCg4Ber nkByMPruVlRxUoL0LUpwmDQ= =EdZa -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070201192641.GA73043>