From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 09:14:18 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ED1816A4CE for ; Sun, 27 Feb 2005 09:14:18 +0000 (GMT) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01C2643D1D for ; Sun, 27 Feb 2005 09:14:18 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0912.wanadoo.fr (SMTP Server) with ESMTP id D536D1C005F9 for ; Sun, 27 Feb 2005 10:14:16 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf0912.wanadoo.fr (SMTP Server) with ESMTP id B095B1C005F8 for ; Sun, 27 Feb 2005 10:14:16 +0100 (CET) X-ME-UUID: 20050227091416723.B095B1C005F8@mwinf0912.wanadoo.fr Date: Sun, 27 Feb 2005 10:14:16 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1123267466.20050227101416@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <20050227071253.GD8778@dan.emsphone.com> References: <738952320.20050226202358@wanadoo.fr> <20050227071253.GD8778@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Constant mysterious SCSI errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 09:14:18 -0000 Dan Nelson writes: > Try lowering the max tags for that drive: "camcontrol tags da0 -N 32". Tried it. I still get the same error; it doesn't seem to have diminished. I get the "queue full" stuff in bursts, then the process trying to do the I/O stalls, then after 30-40 seconds I get one of those huge panel dumps I posted, then the process continues. There doesn't seem to be any data loss. The rest of the system continues to run (it's a 2-processor system, so I don't know if one of the processors is halted when this happens). The problem only seems to arise when there is heavy disk activity. > If that works, you can stick it in rc.local, or add an entry to the > xpt_quirk_table[] in /sys/cam/cam_xpt.c . It probably needs something > similar to the quantum quirk lines. The change to cam_spt.c requires a rebuild of the kernel, right? I found references to SCSI "quirks" on the Net, but not knowing much about SCSI, I wasn't sure which might apply to my situation. Can you explain what all these messages are actually saying? What does it all mean? > I never know what to look for in this output, but most of the time, I > think it's a cabling or termination problem. Reseat all the plugs :) Well, there haven't been any cabling or termination problems in the past eight years, so it seems unlikely that they've appeared today. I think I can safely rule out any type of actual hardware problem. It's either a software configuration problem or a software bug (which might mean a quirk, I suppose). (Note also that these two drives and the controller are on the internal connector of the controller, and although the controller provides an external connector, too, there's nothing connected to it--which further makes cabling or termination problems unlikely.) -- Anthony