Date: Wed, 24 Jan 1996 22:21:42 -0800 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: hackers@freebsd.org Subject: Re: Weird problem, 2940UW -stable, etc. Message-ID: <199601250621.WAA09884@freefall.freebsd.org> In-Reply-To: Your message of "Tue, 23 Jan 1996 20:49:05 PST." <Pine.BSF.3.91.960123203307.349Q-100000@schizo.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>The locks up when INN is running. So I popped a >different disk under /news, and ran fsck on the disk for 30 hours >straight with nary a glitch. Reboot with the RAID disk mounted as /news, >and it failed within an hour. (By fail, I mean I get messages about SCSI >timeout). Note that at no time was any hardware changed or moved, the >only changes here have been fstab changes. Why did you run fsck as your test? Fsck opens the raw device and in doing so may not exercise the same bug if it is a bug. >I have a comm port on the RAID controller, and hooked up a terminal to it >to watch, and I notice that for some reason, it's picking up a SCSI Bus >RESET, right in the middle of things, while the FS is active. Do you get the RESET after the timouts start to happen? Issuing a reset is part of the (very broken at the moment) error recovery code in the driver. If you are getting a reset during normal I/O activity, I'd say your RAID is broken. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601250621.WAA09884>