From owner-freebsd-stable@FreeBSD.ORG Mon Dec 17 19:16:06 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CBC8B9D5 for ; Mon, 17 Dec 2012 19:16:06 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 532918FC19 for ; Mon, 17 Dec 2012 19:16:06 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hm9so2207558wib.13 for ; Mon, 17 Dec 2012 11:16:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=JP1xi1ix40nvU5cyHRgy1XtvxcqqSjNY+PZ9pHX8tFs=; b=wXwLX3opBNtJL46VSGz35iL5Og30xtPK3TtIjMHGW1x0vyiGBJLmVqfNYAtRvBj752 w5UBt1AYxOTIeECUW9Q/NJA7fHdmVM7UcWR/r7zU7kiOFly2UL9CcKLsKYdekuYXaCO7 9tMNhExjmAvIqITi3SztK+DoMagpN3z++DH6qd5StK58QUpTuNWbFDvmwLZD8DcsND8j ChUCurnRMfDSM7ZvyZKcYPL3mtL2oO2Z46jKsaeuVNTDTi5/M/t0uTIQOMiY4owP6pcv Dotf+k0JPp1VXAbeGOBAiTnDFk5zwWv3sL1upanbVGwpx2vYJGqGGIH7YPlV567REXZD bqLQ== MIME-Version: 1.0 Received: by 10.194.20.231 with SMTP id q7mr19069726wje.44.1355771765325; Mon, 17 Dec 2012 11:16:05 -0800 (PST) Sender: jim.harris@gmail.com Received: by 10.217.57.4 with HTTP; Mon, 17 Dec 2012 11:16:05 -0800 (PST) In-Reply-To: <50CF47A5.4090008@digiware.nl> References: <50CEFAC5.8000002@digiware.nl> <572946ED30FA47C69D6DCDD511CF6EB2@multiplay.co.uk> <50CF47A5.4090008@digiware.nl> Date: Mon, 17 Dec 2012 12:16:05 -0700 X-Google-Sender-Auth: i1Ess-14bKi3uz_9cGEfte7ZZAk Message-ID: Subject: Re: Strange CAM errors From: Jim Harris To: Willem Jan Withagen Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Users , Steven Hartland X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2012 19:16:06 -0000 On Mon, Dec 17, 2012 at 9:26 AM, Willem Jan Withagen wrote: > On 2012-12-17 15:38, Steven Hartland wrote: > > Check the smart results of each disk in the array you may have a failing > > disk. > > ----- Original Message ----- From: "Willem Jan Withagen" < > wjw@digiware.nl> > > To: "FreeBSD Stable Users" > > Sent: Monday, December 17, 2012 10:58 AM > > Subject: Strange CAM errors > > > > > >> Hi, > >> > >> I have not noticed this before, but my system rebooted this morning and > >> in the following security report I found a lot of messgaes in the > >> dmesg-part like: > >> > >> +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 > >> +(probe0:arcmsr0:0:16:1): CAM status: Command timeout > >> +(probe0:arcmsr0:0:16:1): Retrying command > >> +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 > >> +(probe0:arcmsr0:0:16:1): CAM status: Command timeout > >> +(probe0:arcmsr0:0:16:1): Retrying command > >> > >> And it seems that bus 16 is: > >> +pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0 > >> +pass6: Fixed Processor SCSI-0 device > >> > >> The system has been running > >> FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed > >> Nov 14 13:25:55 CET 2012 > >> root@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 > >> for already a while. > >> > >> Anybody suggestions as to why I have these messages? > >> > >> They are during the boot sequence, so no smartd talking to the disks at > >> that moment. > >> > >> --WjW > >> > >> ps: dmesg, config, etc.... at: > > >> http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS > >> ps2: upgrading to the most recent 9.1 > > 'mmm, > > Smartd seems to think otherwise... > > 'camcontrol rescan all' actually delivers the same pack of errors. > > --WjW > > The timeouts are occurring on inquiry commands to non-zero LUNs. arcmsr(4) is returning CAM_SEL_TIMEOUT instead of CAM_DEV_NOT_THERE for inquiry commands to this device and LUN > 0. CAM_DEV_NOT_THERE is preferred to remove these types of warnings, and similar patches have gone into for other SCSI drivers recently. Can you try this patch? Index: sys/dev/arcmsr/arcmsr.c =================================================================== --- sys/dev/arcmsr/arcmsr.c (revision 244190) +++ sys/dev/arcmsr/arcmsr.c (working copy) @@ -2439,7 +2439,7 @@ char *buffer=pccb->csio.data_ptr; if (pccb->ccb_h.target_lun) { - pccb->ccb_h.status |= CAM_SEL_TIMEOUT; + pccb->ccb_h.status |= CAM_DEV_NOT_THERE; xpt_done(pccb); return; }