From owner-freebsd-firewire@FreeBSD.ORG Fri Mar 18 03:08:53 2005 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C17516A4CE; Fri, 18 Mar 2005 03:08:53 +0000 (GMT) Received: from relay03.roc.ny.frontiernet.net (relay03.roc.ny.frontiernet.net [66.133.182.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B822743D2D; Fri, 18 Mar 2005 03:08:52 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from filter05.roc.ny.frontiernet.net (filter05.roc.ny.frontiernet.net [66.133.183.72])4CB95358319; Fri, 18 Mar 2005 03:08:52 +0000 (UTC) Received: from relay03.roc.ny.frontiernet.net ([66.133.182.166]) [66.133.183.72]) (amavisd-new, port 10024) with LMTP id 27977-03-70; Fri, 18 Mar 2005 03:08:52 +0000 (UTC) Received: from blacklamb.mykitchentable.net (70-97-221-18.dsl2.elk.ca.frontiernet.net [70.97.221.18])DB94D358078; Fri, 18 Mar 2005 03:08:49 +0000 (UTC) Received: from [192.168.1.3] (bigdaddy.mykitchentable.net [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id AE4C53BF3B1; Thu, 17 Mar 2005 19:08:48 -0800 (PST) Message-ID: <423A4647.5000709@mykitchentable.net> Date: Thu, 17 Mar 2005 19:08:55 -0800 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Questions , freebsd-firewire@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20040701 (2.0) at filter05.roc.ny.frontiernet.net Subject: sbp, camcontrol, and Tagged Queuing X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2005 03:08:53 -0000 I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Thanks, Drew -------- Original Message -------- Subject: Help Interpreting sbp0 Errors Date: Mon, 24 Jan 2005 11:43:21 -0800 From: Drew Tomlinson I've been having problems with vinum volumes since an upgrade from 4.9 to 4.10 which I posted about here: http://docs.freebsd.org/cgi/mid.cgi?41D748F0.1000303 However maybe that is the *symptom* instead of the *problem*. I shut down my system from the console and saw this output: --- BEGIN --- boot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 4 done Uptime: 28d20h48m39s sbp0:0:0 request timeout(mgm orb:0x0a550b14) ... reset start sbp0:0:0 request timeout(cmd orb:0x0a550c4c) ... agent reset (da2:sbp0:0:0:0): Synchronize cache failed, status == 0xb, scsi status == 0x0 sbp0:0:1 request timeout(cmd orb:0x0a5528a4) ... agent reset (da3:sbp0:0:0:1): Synchronize cache failed, status == 0xb, scsi status == 0x0 The operating system has halted. Please press any key to reboot. --- END --- da2 and da3 are two IDE drives in a firewire enclosure. These are also the drives that come up "referenced" after restarting. What do these errors mean? How can I correct them? Is the following section from the sbp man page applicable to my situation? Some (broken) HDDs don't work well with tagged queuing. If you have prob- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew