From owner-freebsd-scsi Mon Apr 6 09:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14502 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 09:44:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14346; Mon, 6 Apr 1998 09:41:50 -0700 (PDT) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2 (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id UAA16807; Mon, 6 Apr 1998 20:19:37 +0400 (MSD) Message-ID: <002001bd6177$dc5c9760$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: "Jordan K. Hubbard" Cc: "Alex" , , , Subject: Re: SCSI errors with latest -current Date: Mon, 6 Apr 1998 20:19:35 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Jordan, Don't (and did not) mean any flame, but if you had read my messages, you would know that they were not about 'Hey do fix this yesterday!'. I just asked someone (you know, not every user of the system has the expertise and time and a free machine to be SCSI hacker) to at least explain what this error means and what (in general terms) might be causing it and are there any ways to overcome this. The list archive search shows that this problem pops up every now and then, but I have seen no positive analysis except 'it should have been fixed in the previous version already'. I was disappointed not by the not-fixing of the problem (though I would appreciate seeing it fixed as the server dying in the middle of the night during backup is not a pleasant view for sysadmin). What gave me the unpleasant surprise was the complete indifference of readers (quite unusual for the FreeBSD _community_). Yours Genie -----Original Message----- From: Jordan K. Hubbard To: Eugene Radchenko Cc: Alex ; ache@nagual.pp.ru ; scsi@FreeBSD.ORG ; current@FreeBSD.ORG Date: Monday, April 06, 1998 4:05 PM Subject: Re: SCSI errors with latest -current >> As I tried to shout all over the SCSI list recently (to no avail), this is >> not limited to -current or 2.2.5. I had something like this even in 2.1 >> (though not as drastic -- just dump died and not the whole system). I have >> the feeling that 2.1 had not done tagged queueing yet. > >Things don't get fixed by shouting, they get fixed by fixing. That's >free software. Feel free, Eugene! ;-) > > Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message