From owner-freebsd-hackers Wed Feb 25 13:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21858 for freebsd-hackers-outgoing; Wed, 25 Feb 1998 13:19:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21360 for ; Wed, 25 Feb 1998 13:17:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA21029; Wed, 25 Feb 1998 13:16:08 -0800 (PST) Message-Id: <199802252116.NAA21029@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Denninger cc: hackers@FreeBSD.ORG Subject: Re: SCSI Sense ASC 11, ASCQ 0x0c - Unrecovered read errors In-reply-to: Your message of "Wed, 25 Feb 1998 15:10:42 CST." <19980225151042.07314@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Feb 1998 13:16:05 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the system is not properly dealing with EIO conditions, that is > > certainly a bug, but your suggested fix is not a correct solution. > > This condition, right now, causes a *HANG* if it happens on *DATA FILES*. > > Not a panic, not an error return, not termination of the offending process. > A hard system crash which requires a RESET to recover from. Sure. We got that the first time. But you haven't proposed a useful solution. Even just something that returned a read error would be fine. But leaping up and down and screaming about it isn't going to get anything done. See the previous discussion inre: big sticks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message