From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 20 11:07:10 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7287B106564A
for <freebsd-scsi@FreeBSD.org>; Mon, 20 Jun 2011 11:07:10 +0000 (UTC)
(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 583498FC16
for <freebsd-scsi@FreeBSD.org>; Mon, 20 Jun 2011 11:07:10 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5KB7A7R098230
for <freebsd-scsi@FreeBSD.org>; Mon, 20 Jun 2011 11:07:10 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5KB79ue098228
for freebsd-scsi@FreeBSD.org; Mon, 20 Jun 2011 11:07:09 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Date: Mon, 20 Jun 2011 11:07:09 GMT
Message-Id: <201106201107.p5KB79ue098228@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: gnats set sender to
owner-bugmaster@FreeBSD.org using -f
From: FreeBSD bugmaster <bugmaster@FreeBSD.org>
To: freebsd-scsi@FreeBSD.org
Cc:
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 11:07:10 -0000
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic
o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after
o kern/153514 scsi [cam] [panic] CAM related panic
o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem
o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden
o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10
o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c
s kern/149927 scsi [cam] hard drive not stopped before removing power dur
o kern/148083 scsi [aac] Strange device reporting
o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp
o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con
o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb
o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg
o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss
o kern/142351 scsi [mpt] LSILogic driver performance problems
o kern/141934 scsi [cam] [patch] add support for SEAGATE DAT Scopion 130
o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device
o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive
o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri
o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up
o kern/127717 scsi [ata] [patch] [request] - support write cache toggling
o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674 scsi [ahc] ahc driver dumping
o kern/123520 scsi [ahd] unable to boot from net while using ahd
o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487 scsi [sg] scsi_sg incompatible with scanners
o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s
o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression]
o kern/92798 scsi [ahc] SCSI problem with timeouts
o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device
o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system
o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb
o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598 scsi wire down of scsi devices conflicts with config
s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di
o bin/57088 scsi [cam] [patch] for a possible fd leak in libcam.c
o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than
o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce
47 problems total.
From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 21 12:10:14 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 281EA106566C
for <freebsd-scsi@hub.freebsd.org>;
Tue, 21 Jun 2011 12:10:14 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 184638FC13
for <freebsd-scsi@hub.freebsd.org>;
Tue, 21 Jun 2011 12:10:14 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5LCAD4w030842
for <freebsd-scsi@freefall.freebsd.org>; Tue, 21 Jun 2011 12:10:13 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5LCAD3C030841;
Tue, 21 Jun 2011 12:10:13 GMT (envelope-from gnats)
Date: Tue, 21 Jun 2011 12:10:13 GMT
Message-Id: <201106211210.p5LCAD3C030841@freefall.freebsd.org>
To: freebsd-scsi@FreeBSD.org
From: Erwan Martin <emartin@lanestel.fr>
Cc:
Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erwan Martin <emartin@lanestel.fr>
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 12:10:14 -0000
The following reply was made to PR kern/157770; it has been noted by GNATS.
From: Erwan Martin <emartin@lanestel.fr>
To: bug-followup@FreeBSD.org, martin.birgmeier@aon.at
Cc:
Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
Date: Tue, 21 Jun 2011 13:42:18 +0200
I'm having the same problem.
The windows XP initiator works perfectly but iscsi_initiator does not.
The initiator system is:
FreeBSD fbsd.localdomain 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Jun 10
10:17:58 CEST 2011
root@fbsd.localdomain:/usr/obj/usr/src/sys/ISCSIKERNEL i386
On the target:
Jun 21 11:06:49 hostname istgt[11438]: Login(discovery) from
iqn.2011-06.net.example.tests:whatever (192.168.3.205) on449423030,
TSIH=4, CID=1, HeaderDigest=off, DataDigest=off
Jun 21 11:06:49 hostname istgt[11438]:
istgt_iscsi.c:1848:istgt_iscsi_check_values: ***ERROR***
FirstBurstLength(262144) > MaxBurstLength(131072)
Jun 21 11:06:49 hostname istgt[11438]:
istgt_iscsi.c:2559:istgt_iscsi_op_login: ***ERROR***
iscsi_check_values() failed
Jun 21 11:06:49 hostname istgt[11438]:
istgt_iscsi.c:4545:istgt_iscsi_execute: ***ERROR*** iscsi_op_login() failed
Jun 21 11:06:49 hostname istgt[11438]: istgt_iscsi.c:5156:worker:
***ERROR*** iscsi_execute() failed on
dummy,t,0x0001(iqual175,i,0x804449423030)
I do not experience any system crash however.
This bug can be repeated on my system.
From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 22 06:21:41 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 38C6C1065722
for <freebsd-scsi@FreeBSD.org>; Wed, 22 Jun 2011 06:21:41 +0000 (UTC)
(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
by mx1.freebsd.org (Postfix) with ESMTP id EBA448FC1B
for <freebsd-scsi@FreeBSD.org>; Wed, 22 Jun 2011 06:21:40 +0000 (UTC)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
by kabab.cs.huji.ac.il with esmtp
id 1QZGok-000DHg-Mp; Wed, 22 Jun 2011 09:21:38 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: Erwan Martin <emartin@lanestel.fr>
In-reply-to: <201106211210.p5LCAD3C030841@freefall.freebsd.org>
References: <201106211210.p5LCAD3C030841@freefall.freebsd.org>
Comments: In-reply-to Erwan Martin <emartin@lanestel.fr>
message dated "Tue, 21 Jun 2011 12:10:13 +0000."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Jun 2011 09:21:38 +0300
From: Daniel Braniss <danny@cs.huji.ac.il>
Message-ID: <E1QZGok-000DHg-Mp@kabab.cs.huji.ac.il>
Cc: freebsd-scsi@FreeBSD.org
Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 06:21:41 -0000
> The following reply was made to PR kern/157770; it has been noted by GNATS.
>
> From: Erwan Martin <emartin@lanestel.fr>
> To: bug-followup@FreeBSD.org, martin.birgmeier@aon.at
> Cc:
> Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
> Date: Tue, 21 Jun 2011 13:42:18 +0200
>
> I'm having the same problem.
> The windows XP initiator works perfectly but iscsi_initiator does not.
>
> The initiator system is:
> FreeBSD fbsd.localdomain 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Jun 10
> 10:17:58 CEST 2011
> root@fbsd.localdomain:/usr/obj/usr/src/sys/ISCSIKERNEL i386
>
> On the target:
> Jun 21 11:06:49 hostname istgt[11438]: Login(discovery) from
> iqn.2011-06.net.example.tests:whatever (192.168.3.205) on449423030,
> TSIH=4, CID=1, HeaderDigest=off, DataDigest=off
> Jun 21 11:06:49 hostname istgt[11438]:
> istgt_iscsi.c:1848:istgt_iscsi_check_values: ***ERROR***
> FirstBurstLength(262144) > MaxBurstLength(131072)
> Jun 21 11:06:49 hostname istgt[11438]:
> istgt_iscsi.c:2559:istgt_iscsi_op_login: ***ERROR***
> iscsi_check_values() failed
> Jun 21 11:06:49 hostname istgt[11438]:
> istgt_iscsi.c:4545:istgt_iscsi_execute: ***ERROR*** iscsi_op_login() failed
> Jun 21 11:06:49 hostname istgt[11438]: istgt_iscsi.c:5156:worker:
> ***ERROR*** iscsi_execute() failed on
> dummy,t,0x0001(iqual175,i,0x804449423030)
>
> I do not experience any system crash however.
>
> This bug can be repeated on my system.
either add
maxBurstLength = 262144
to the iscsi.conf, or
iscontrol ... maxBurstLength=262144
danny
From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 22 07:40:22 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1A4B9106570D
for <freebsd-scsi@hub.freebsd.org>;
Wed, 22 Jun 2011 07:40:22 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id E53A98FC12
for <freebsd-scsi@hub.freebsd.org>;
Wed, 22 Jun 2011 07:40:21 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5M7eL2e050027
for <freebsd-scsi@freefall.freebsd.org>; Wed, 22 Jun 2011 07:40:21 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5M7eL5p050026;
Wed, 22 Jun 2011 07:40:21 GMT (envelope-from gnats)
Date: Wed, 22 Jun 2011 07:40:21 GMT
Message-Id: <201106220740.p5M7eL5p050026@freefall.freebsd.org>
To: freebsd-scsi@FreeBSD.org
From: Daniel Braniss <danny@cs.huji.ac.il>
Cc:
Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Braniss <danny@cs.huji.ac.il>
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 07:40:22 -0000
The following reply was made to PR kern/157770; it has been noted by GNATS.
From: Daniel Braniss <danny@cs.huji.ac.il>
To: bug-followup@FreeBSD.org,
martin.birgmeier@aon.at
Cc:
Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic
Date: Wed, 22 Jun 2011 10:12:12 +0300
There are 2 issues here, and only one causes the panic.
issue 1: mismatch of negotiated values might cause hangs/panics when =
trying to kill iscontrol
this is in my todo list.
issue 2: somehow -to be investigated- iscontrol and istgt don't =
negotiate FirstBurstLength and
MaxBurtsLength correctly. The workaround is either to reduce =
MaxBurstLength in istgt conf, or
increase it in iscsi,conf
danny
From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 23 21:15:30 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E2B5D1065672;
Thu, 23 Jun 2011 21:15:30 +0000 (UTC)
(envelope-from joe@gracenpeace.net)
Received: from shorty.gracenpeace.net (shorty.gracenpeace.net [209.181.242.73])
by mx1.freebsd.org (Postfix) with ESMTP id BC7868FC19;
Thu, 23 Jun 2011 21:15:30 +0000 (UTC)
Received: from [127.0.0.1] (mail.holidaycompanies.com [209.98.45.253])
by shorty.gracenpeace.net (Postfix) with ESMTP id 0C7C3439012;
Thu, 23 Jun 2011 14:41:54 -0500 (CDT)
Message-ID: <4E03A647.5070501@gracenpeace.net>
Date: Thu, 23 Jun 2011 15:47:03 -0500
From: Joe in MPLS <joe@gracenpeace.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: scsi@freebsd.org, stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: LTO3 tape drive not detected
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 21:15:31 -0000
This was originally posted on the freebsd-questions list. It was
suggested that I post it here:
I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added
an (HP branded) LSI Logic single channel SCSI 320 card and attached an
HP Ultrium 920 LTO3 tape drive.
The system sees the SCSI controller as mpt0, and it seems to know
there's something at SCSI ID 4, but I get an "AutoSense Failed" for
hba/id/lun 0:4:0 at boot and subsequent camcontrol rescans.
I checked the supported hardware doc for the release but it doesn't get
very specific about tape drives. This is my first experience with LTO3
tape. I was hoping that I'd automagically get a /dev/sa0 device like I
always did with my old DLT drives but it wasn't to be this time.
Is there a way to make this drive work?
From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 23 23:10:32 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D1AE5106564A
for <scsi@freebsd.org>; Thu, 23 Jun 2011 23:10:32 +0000 (UTC)
(envelope-from mj@feral.com)
Received: from ns1.feral.com (ns1.feral.com [192.67.166.1])
by mx1.freebsd.org (Postfix) with ESMTP id 96B638FC08
for <scsi@freebsd.org>; Thu, 23 Jun 2011 23:10:32 +0000 (UTC)
Received: from ns1.feral.com (localhost [127.0.0.1])
by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p5NMcG70026430
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Thu, 23 Jun 2011 15:38:16 -0700 (PDT) (envelope-from mj@feral.com)
Received: from localhost (mjacob@localhost)
by ns1.feral.com (8.14.4/8.14.4/Submit) with ESMTP id p5NMcG6V026427;
Thu, 23 Jun 2011 15:38:16 -0700 (PDT) (envelope-from mj@feral.com)
X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs
Date: Thu, 23 Jun 2011 15:38:16 -0700 (PDT)
From: Matthew Jacob <mj@feral.com>
To: Joe in MPLS <joe@gracenpeace.net>
In-Reply-To: <4E03A647.5070501@gracenpeace.net>
Message-ID: <alpine.BSF.2.00.1106231533590.26375@ns1.feral.com>
References: <4E03A647.5070501@gracenpeace.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6
(ns1.feral.com [127.0.0.1]); Thu, 23 Jun 2011 15:38:16 -0700 (PDT)
Cc: scsi@freebsd.org
Subject: Re: LTO3 tape drive not detected
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mj@feral.com
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 23:10:32 -0000
Hmm, haven't had real drives to play with in a while, and don't recall
ever attaching one through an MPT. Do you have another SCSI adapter?
Autosense fail for mpt means that the MPT controller firmware was unable
to retrieve sense data for a command. We just give up on that.
You might get into the MPT BIOS settings and set narrow/async for the
device just to see if that will work.
On Thu, 23 Jun 2011, Joe in MPLS wrote:
> This was originally posted on the freebsd-questions list. It was suggested
> that I post it here:
>
> I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added an (HP
> branded) LSI Logic single channel SCSI 320 card and attached an HP Ultrium
> 920 LTO3 tape drive.
>
> The system sees the SCSI controller as mpt0, and it seems to know there's
> something at SCSI ID 4, but I get an "AutoSense Failed" for hba/id/lun 0:4:0
> at boot and subsequent camcontrol rescans.
>
> I checked the supported hardware doc for the release but it doesn't get very
> specific about tape drives. This is my first experience with LTO3 tape. I was
> hoping that I'd automagically get a /dev/sa0 device like I always did with my
> old DLT drives but it wasn't to be this time.
>
> Is there a way to make this drive work?
>
>
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"
>
From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 24 01:47:39 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 528C81065670;
Fri, 24 Jun 2011 01:47:39 +0000 (UTC)
(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10])
by mx1.freebsd.org (Postfix) with ESMTP id C4B3D8FC12;
Fri, 24 Jun 2011 01:47:37 +0000 (UTC)
Received: from ur.dons.net.au (ppp203-122-208-108.lns5.adl6.internode.on.net
[203.122.208.108]) (authenticated bits=0)
by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p5O1FAFP006452
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Fri, 24 Jun 2011 10:45:12 +0930 (CST)
(envelope-from doconnor@gsoft.com.au)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
In-Reply-To: <4E03A647.5070501@gracenpeace.net>
Date: Fri, 24 Jun 2011 10:45:10 +0930
Content-Transfer-Encoding: quoted-printable
Message-Id: <F88F168E-F70F-4640-823C-33689D9CDB92@gsoft.com.au>
References: <4E03A647.5070501@gracenpeace.net>
To: Joe in MPLS <joe@gracenpeace.net>
X-Mailer: Apple Mail (2.1084)
X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC
X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10
Cc: stable@freebsd.org, scsi@freebsd.org
Subject: Re: LTO3 tape drive not detected
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 01:47:39 -0000
On 24/06/2011, at 6:17, Joe in MPLS wrote:
> This was originally posted on the freebsd-questions list. It was =
suggested that I post it here:
>=20
> I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added =
an (HP branded) LSI Logic single channel SCSI 320 card and attached an =
HP Ultrium 920 LTO3 tape drive.
>=20
> The system sees the SCSI controller as mpt0, and it seems to know =
there's something at SCSI ID 4, but I get an "AutoSense Failed" for =
hba/id/lun 0:4:0 at boot and subsequent camcontrol rescans.
>=20
> I checked the supported hardware doc for the release but it doesn't =
get very specific about tape drives. This is my first experience with =
LTO3 tape. I was hoping that I'd automagically get a /dev/sa0 device =
like I always did with my old DLT drives but it wasn't to be this time.
>=20
> Is there a way to make this drive work?
I'd check the cabling etc..
I have an LTO2 drive that "Just works (tm)".
Can you boot a Linux ISO and see if that finds it?
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 24 02:36:23 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 27906106564A
for <scsi@freebsd.org>; Fri, 24 Jun 2011 02:36:23 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from qmta06.emeryville.ca.mail.comcast.net
(qmta06.emeryville.ca.mail.comcast.net [76.96.30.56])
by mx1.freebsd.org (Postfix) with ESMTP id 0F0B98FC16
for <scsi@freebsd.org>; Fri, 24 Jun 2011 02:36:22 +0000 (UTC)
Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12])
by qmta06.emeryville.ca.mail.comcast.net with comcast
id zcVr1g0040FhH24A6ePAGP; Fri, 24 Jun 2011 02:23:10 +0000
Received: from koitsu.dyndns.org ([67.180.84.87])
by omta08.emeryville.ca.mail.comcast.net with comcast
id zeP81g0071t3BNj8UePBBP; Fri, 24 Jun 2011 02:23:15 +0000
Received: by icarus.home.lan (Postfix, from userid 1000)
id 8E2C8102C36; Thu, 23 Jun 2011 19:23:03 -0700 (PDT)
Date: Thu, 23 Jun 2011 19:23:03 -0700
From: Jeremy Chadwick <freebsd@jdc.parodius.com>
To: Daniel O'Connor <doconnor@gsoft.com.au>
Message-ID: <20110624022303.GA19128@icarus.home.lan>
References: <4E03A647.5070501@gracenpeace.net>
<F88F168E-F70F-4640-823C-33689D9CDB92@gsoft.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F88F168E-F70F-4640-823C-33689D9CDB92@gsoft.com.au>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: stable@freebsd.org, Joe in MPLS <joe@gracenpeace.net>, scsi@freebsd.org
Subject: Re: LTO3 tape drive not detected
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 02:36:23 -0000
On Fri, Jun 24, 2011 at 10:45:10AM +0930, Daniel O'Connor wrote:
>
> On 24/06/2011, at 6:17, Joe in MPLS wrote:
> > This was originally posted on the freebsd-questions list. It was suggested that I post it here:
> >
> > I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added an (HP branded) LSI Logic single channel SCSI 320 card and attached an HP Ultrium 920 LTO3 tape drive.
> >
> > The system sees the SCSI controller as mpt0, and it seems to know there's something at SCSI ID 4, but I get an "AutoSense Failed" for hba/id/lun 0:4:0 at boot and subsequent camcontrol rescans.
> >
> > I checked the supported hardware doc for the release but it doesn't get very specific about tape drives. This is my first experience with LTO3 tape. I was hoping that I'd automagically get a /dev/sa0 device like I always did with my old DLT drives but it wasn't to be this time.
> >
> > Is there a way to make this drive work?
>
> I'd check the cabling etc..
>
> I have an LTO2 drive that "Just works (tm)".
>
> Can you boot a Linux ISO and see if that finds it?
I would recommend you two compare comparing DIP switch or jumper
settings, as well as firmware versions. Many tape drives have
"compatibility" switches, and firmware versions play a huge role.
SCSI card settings (within the SCSI BIOS) would also play a large role
here.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, US |
| Making life hard for others since 1977. PGP 4BD6C0CB |
From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 24 15:20:04 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2B17E1065673
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 15:20:04 +0000 (UTC)
(envelope-from pz-freebsd-scsi@ziemba.us)
Received: from ziemba.us (osmtp.ziemba.us [208.106.105.149])
by mx1.freebsd.org (Postfix) with ESMTP id D345A8FC17
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 15:20:03 +0000 (UTC)
Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1])
by hairball.ziemba.us (8.14.4/8.14.4) with ESMTP id p5OEvUbf014355
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 07:57:30 -0700 (PDT)
(envelope-from pz-freebsd-scsi@ziemba.us)
Received: (from mailnull@localhost)
by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p5OEvURW014354
for freebsd-scsi@freebsd.org; Fri, 24 Jun 2011 07:57:30 -0700 (PDT)
(envelope-from pz-freebsd-scsi@ziemba.us)
X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to
pz-freebsd-scsi@ziemba.us using -f
Received: (from news@localhost)
by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p5OEvUV2014321
for treehouse-mail-freebsd-scsi@hairball.treehouse.napa.ca.us;
Fri, 24 Jun 2011 07:57:30 -0700 (PDT) (envelope-from news)
From: "G. Paul Ziemba" <pz-freebsd-scsi@ziemba.us>
To: freebsd-scsi@freebsd.org
Date: Fri, 24 Jun 2011 14:57:29 +0000 (UTC)
Message-id: <iu28kp$dvg$1@hairball.ziemba.us>
Errors-to: "G. Paul Ziemba" <paul+usenet@w6yx.stanford.edu>
Subject: making a predictable passX name
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: paul+usenet@w6yx.stanford.edu
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 15:20:04 -0000
Is there a way to set up a constant name for a /dev/passX
device? (Or maybe there is a better way to solve the problem)
% uname -r
8.2-PRERELEASE
% pkg_info | grep amanda-server
amanda-server-3.2.1,1 The Advanced Maryland Automatic Network Disk Archiver (serv)
I'm setting up a Dell Powervault 122T with LTO2 drive to operate
with amanda. I seems to me that chg-robot is the best choice of
changer.
chg-robot uses mtx, which seems to require the name of the /dev/passX
device corresponding to the changer (attached as /dev/ch0).
Therefore, I'm trying to create a link with a constant name
that points to the arbitrary /dev/passX name. I plan to use this
constant name in the amanda config file.
I can manually run "camcontrol periphlist ch0" and obtain the
matching pass device name, so in theory I can write a small
script to create a link such as /dev/ch0.pass -> /dev/passX
and then specify /dev/ch0.pass in the amanda config file.
I wrote the following in /etc/devd.conf:
attach 100 {
device-name "ch[0-9]+";
action "camcontrol periphlist $device-name|grep pass|sed -e 's/:.*\$//'|xargs -I PASS ln -s /dev/PASS /dev/$device-name.pass; logger added ch pass link";
};
detach 100 {
device-name "ch[0-9]+";
action "rm /dev/$device-name.pass; logger removed ch pass link";
};
I also tried the above with just the "logger" parts in the actions.
However, the actions do not seem to be invoked when the ch0 device
is attached (power-on + camcontrol rescan + messages in /var/log/messages).
Maybe devd does not get an "attach" event when ch attaches?
Is there another way to trigger on the attach/detach events for /dev/chX?
Or a way to hard-wire assignment of the /dev/passX names?
Many thanks for your advice.
--
G. Paul Ziemba
FreeBSD unix:
7:56AM up 41 days, 11:37, 34 users, load averages: 0.60, 0.66, 0.63
From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 24 16:30:03 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1AEEF1065672
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 16:30:03 +0000 (UTC)
(envelope-from bartsch@dssgmbh.de)
Received: from mail.incore.de (dss.incore.de [195.145.1.138])
by mx1.freebsd.org (Postfix) with ESMTP id 9E8B28FC13
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 16:30:02 +0000 (UTC)
Received: from inetmail.dmz (inetmail.dmz [10.3.0.3])
by mail.incore.de (Postfix) with ESMTP id ED3EC5FD1D;
Fri, 24 Jun 2011 18:13:50 +0200 (CEST)
X-Virus-Scanned: amavisd-new at incore.de
Received: from mail.incore.de ([10.3.0.3])
by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024)
with LMTP id zdfxdiIS0nLs; Fri, 24 Jun 2011 18:13:48 +0200 (CEST)
Received: from mail.incore (fwintern.dmz [10.0.0.253])
by mail.incore.de (Postfix) with ESMTP id C53AF5FD16;
Fri, 24 Jun 2011 18:13:48 +0200 (CEST)
Received: from pcadmin.incore (pcadmin.incore [192.168.0.140])
by mail.incore (Postfix) with ESMTPSA id B132145050;
Fri, 24 Jun 2011 18:13:48 +0200 (CEST)
Message-ID: <4E04B7BC.6010707@dssgmbh.de>
Date: Fri, 24 Jun 2011 18:13:48 +0200
From: Alfred Bartsch <bartsch@dssgmbh.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE;
rv:1.9.1.16) Gecko/20110126 Thunderbird/3.0.11
MIME-Version: 1.0
To: paul+usenet@w6yx.stanford.edu
References: <iu28kp$dvg$1@hairball.ziemba.us>
In-Reply-To: <iu28kp$dvg$1@hairball.ziemba.us>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-scsi@freebsd.org
Subject: Re: making a predictable passX name
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 16:30:03 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 24.06.2011 16:57, schrieb G. Paul Ziemba:
> Is there a way to set up a constant name for a /dev/passX
> device? (Or maybe there is a better way to solve the problem)
>
> % uname -r
> 8.2-PRERELEASE
>
> % pkg_info | grep amanda-server
> amanda-server-3.2.1,1 The Advanced Maryland Automatic Network Disk Archiver (serv)
>
> I'm setting up a Dell Powervault 122T with LTO2 drive to operate
> with amanda. I seems to me that chg-robot is the best choice of
> changer.
>
> chg-robot uses mtx, which seems to require the name of the /dev/passX
> device corresponding to the changer (attached as /dev/ch0).
> Therefore, I'm trying to create a link with a constant name
> that points to the arbitrary /dev/passX name. I plan to use this
> constant name in the amanda config file.
>
> I can manually run "camcontrol periphlist ch0" and obtain the
> matching pass device name, so in theory I can write a small
> script to create a link such as /dev/ch0.pass -> /dev/passX
> and then specify /dev/ch0.pass in the amanda config file.
>
> I wrote the following in /etc/devd.conf:
>
> attach 100 {
> device-name "ch[0-9]+";
> action "camcontrol periphlist $device-name|grep pass|sed -e 's/:.*\$//'|xargs -I PASS ln -s /dev/PASS /dev/$device-name.pass; logger added ch pass link";
> };
>
> detach 100 {
> device-name "ch[0-9]+";
> action "rm /dev/$device-name.pass; logger removed ch pass link";
> };
>
> I also tried the above with just the "logger" parts in the actions.
>
> However, the actions do not seem to be invoked when the ch0 device
> is attached (power-on + camcontrol rescan + messages in /var/log/messages).
> Maybe devd does not get an "attach" event when ch attaches?
>
> Is there another way to trigger on the attach/detach events for /dev/chX?
> Or a way to hard-wire assignment of the /dev/passX names?
>
You can achieve this behaviour via editing /boot/device.hints:
...
# SCSI tape peripherals
#
hint.scbus.0.at="mpt0"
hint.scbus.0.bus="0"
#
# Drive
hint.sa.0.at="scbus0"
hint.sa.0.target="4"
hint.sa.0.lun="0"
hint.pass.0.at="scbus0"
hint.pass.0.target="4"
hint.pass.0.lun="0"
# Changer
hint.ch.0.at="scbus0"
hint.ch.0.target="4"
hint.ch.0.lun="1"
hint.pass.1.at="scbus0"
hint.pass.1.target="4"
hint.pass.1.lun="1"
#
all You have to know is:
- - the SCSI driver (in our case mpt) with its associated bus number (0)
- - target and lun of drive and changer
it is then possible to freely choose a pass device number, in this example:
SCSI_ID 0:4:0 gets pass0 (drive), SCSI_ID 0:4:1 gets pass1 (changer)
changes take effect after reboot, HTH.
- --
Alfred Bartsch
Data-Service GmbH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4Et7wACgkQ5QGe2JdVf3gsrwCguAGB3JaOB2OQA6BQbstwgnaE
K8YAn0F+m+S1UN6SR6WlMuPqxQmtktyi
=WyTG
-----END PGP SIGNATURE-----
From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 24 23:58:30 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6944E106564A
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 23:58:30 +0000 (UTC)
(envelope-from pz-freebsd-scsi@ziemba.us)
Received: from ziemba.us (osmtp.ziemba.us [208.106.105.149])
by mx1.freebsd.org (Postfix) with ESMTP id 3F6398FC0C
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 23:58:29 +0000 (UTC)
Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1])
by hairball.ziemba.us (8.14.4/8.14.4) with ESMTP id p5ONwTqM088266
for <freebsd-scsi@freebsd.org>; Fri, 24 Jun 2011 16:58:29 -0700 (PDT)
(envelope-from pz-freebsd-scsi@ziemba.us)
Received: (from mailnull@localhost)
by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p5ONwTSq088265
for freebsd-scsi@freebsd.org; Fri, 24 Jun 2011 16:58:29 -0700 (PDT)
(envelope-from pz-freebsd-scsi@ziemba.us)
X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to
pz-freebsd-scsi@ziemba.us using -f
Received: (from news@localhost)
by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p5ONwTck088231
for treehouse-mail-freebsd-scsi@hairball.treehouse.napa.ca.us;
Fri, 24 Jun 2011 16:58:29 -0700 (PDT) (envelope-from news)
From: "G. Paul Ziemba" <pz-freebsd-scsi@ziemba.us>
To: freebsd-scsi@freebsd.org
Date: Fri, 24 Jun 2011 23:58:29 +0000 (UTC)
Message-id: <iu38b5$2ksj$1@hairball.ziemba.us>
References: <4E04B7BC.6010707@dssgmbh.de>
Errors-to: "G. Paul Ziemba" <paul+usenet@w6yx.stanford.edu>
Subject: Re: making a predictable passX name
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: paul+usenet@w6yx.stanford.edu
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 23:58:30 -0000
bartsch@dssgmbh.de (Alfred Bartsch) writes:
>Am 24.06.2011 16:57, schrieb G. Paul Ziemba:
>> Is there another way to trigger on the attach/detach events for /dev/chX?
>> Or a way to hard-wire assignment of the /dev/passX names?
>>
>You can achieve this behaviour via editing /boot/device.hints:
>...
># SCSI tape peripherals
>#
>hint.scbus.0.at="mpt0"
>hint.scbus.0.bus="0"
>#
># Drive
>hint.sa.0.at="scbus0"
>hint.sa.0.target="4"
>hint.sa.0.lun="0"
>hint.pass.0.at="scbus0"
>hint.pass.0.target="4"
>hint.pass.0.lun="0"
># Changer
>hint.ch.0.at="scbus0"
>hint.ch.0.target="4"
>hint.ch.0.lun="1"
>hint.pass.1.at="scbus0"
>hint.pass.1.target="4"
>hint.pass.1.lun="1"
>#
>all You have to know is:
>- - the SCSI driver (in our case mpt) with its associated bus number (0)
>- - target and lun of drive and changer
>it is then possible to freely choose a pass device number, in this example:
>SCSI_ID 0:4:0 gets pass0 (drive), SCSI_ID 0:4:1 gets pass1 (changer)
>changes take effect after reboot, HTH.
Aha. I only looked at the man page for pass(4); I should have
looked at scsi(4).
Thanks!
--
G. Paul Ziemba
FreeBSD unix:
4:56PM up 41 days, 20:37, 32 users, load averages: 0.89, 0.77, 0.69
From owner-freebsd-scsi@FreeBSD.ORG Sat Jun 25 01:43:13 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5A0A3106564A;
Sat, 25 Jun 2011 01:43:13 +0000 (UTC)
(envelope-from joachim@tingvold.com)
Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54])
by mx1.freebsd.org (Postfix) with ESMTP id 15DD38FC1D;
Sat, 25 Jun 2011 01:43:12 +0000 (UTC)
Received: from aannecy-552-1-282-248.w83-201.abo.wanadoo.fr ([83.201.250.248]
helo=keklolwtf.home)
by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16)
(Exim 4.72) (envelope-from <joachim@tingvold.com>)
id 1QaHhp-0000aj-Ev; Sat, 25 Jun 2011 03:30:42 +0200
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Joachim Tingvold <joachim@tingvold.com>
In-Reply-To: <20110225183351.GA31590@nargothrond.kdm.org>
Date: Sat, 25 Jun 2011 03:30:37 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <8AFCE2C0-A87D-414B-912F-C80C158B6D94@tingvold.com>
References: <20110204180011.GA38067@nargothrond.kdm.org>
<DE11FC96-06DB-479F-8673-B9ACE2805390@tingvold.com>
<20110208201310.GA97635@nargothrond.kdm.org>
<4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com>
<20110218171619.GB78796@nargothrond.kdm.org>
<318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com>
<20110221155041.GA37922@nargothrond.kdm.org>
<3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com>
<20110221214544.GA43886@nargothrond.kdm.org>
<2E532F21-B969-4216-9765-BC1CC1EAB522@tingvold.com>
<20110225183351.GA31590@nargothrond.kdm.org>
To: Kenneth D. Merry <ken@freebsd.org>
X-Mailer: Apple Mail (2.1076)
Cc: freebsd-scsi@freebsd.org, Alexander Motin <mav@freebsd.org>
Subject: Re: mps0-troubles
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 01:43:13 -0000
On Fri, Feb 25, 2011, at 19:33:51PM GMT+01:00, Kenneth D. Merry wrote:
> I just checked the change into -current, I'll merge it to -stable
> next week.
I'm back! Missed me? :-D
After running fine for a while, I decided to do some more testing.
Usual 'dd' in a while-loop over the night, and woke up to this;
###
mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 0
mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
mps0: mpssas_remove_complete on target 0x0027, IOCStatus= 0x0
(da7:mps0:0:39:0): lost device
(da7:mps0:0:39:0): Invalidating pack
(da7:mps0:0:39:0): Invalidating pack
(da7:mps0:0:39:0): Invalidating pack
(da7:mps0:0:39:0): Invalidating pack
(da7:mps0:0:39:0): Synchronize cache failed, status == 0xa, scsi
status == 0x0
(da7:mps0:0:39:0): removing device entry
da7 at mps0 bus 0 scbus0 target 39 lun 0
da7: <ATA WDC WD10EACS-00Z 1B01> Fixed Direct Access SCSI-5 device
da7: 300.000MB/s transfers
da7: Command Queueing enabled
da7: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
###
Now, the disk was present at the time I checked, as camcontrol confirms;
[root@filserver /storage/tmp]# camcontrol devlist|grep da7
<ATA WDC WD10EACS-00Z 1B01> at scbus0 target 39 lun 0 (pass8,da7)
However, the disk was marked as "REMOVED" by 'zpool status';
###
[jocke@filserver /storage/tmp]$ zpool status
pool: storage
state: DEGRADED
NAME STATE READ WRITE CKSUM
storage DEGRADED 0 0 0
raidz2-0 ONLINE 0 0 0
da8 ONLINE 0 0 0
da9 ONLINE 0 0 0
da10 ONLINE 0 0 0
da11 ONLINE 0 0 0
da15 ONLINE 0 0 0
da16 ONLINE 0 0 0
raidz2-1 DEGRADED 0 0 0
da0 ONLINE 0 0 0
da1 ONLINE 0 0 0
da2 ONLINE 0 0 0
da3 ONLINE 0 0 0
da4 ONLINE 0 0 0
da5 ONLINE 0 0 0
da6 ONLINE 0 0 0
da7 REMOVED 0 0 0
da12 ONLINE 0 0 0
da13 ONLINE 0 0 0
spares
da14 AVAIL
###
A quick 'zpool online storage da7' works fine, as suspected, and pool
is resilvering at the moment.
I find it a bit worrisome that a disk was removed like that. It
_could_ be that the disk isn't completely good, however, due to my
previous experiences with mps, I suspect the disk is fine (smartctl-
readouts on the disk seems to be good as well).
--
Joachim
From owner-freebsd-scsi@FreeBSD.ORG Sat Jun 25 03:07:50 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 00C131065670
for <freebsd-scsi@freebsd.org>; Sat, 25 Jun 2011 03:07:50 +0000 (UTC)
(envelope-from ken@kdm.org)
Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81])
by mx1.freebsd.org (Postfix) with ESMTP id 80C008FC08
for <freebsd-scsi@freebsd.org>; Sat, 25 Jun 2011 03:07:49 +0000 (UTC)
Received: from nargothrond.kdm.org (localhost [127.0.0.1])
by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p5P2jYmc086730;
Fri, 24 Jun 2011 20:45:34 -0600 (MDT)
(envelope-from ken@nargothrond.kdm.org)
Received: (from ken@localhost)
by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p5P2jXsR086729;
Fri, 24 Jun 2011 20:45:33 -0600 (MDT) (envelope-from ken)
Date: Fri, 24 Jun 2011 20:45:33 -0600
From: "Kenneth D. Merry" <ken@freebsd.org>
To: Joachim Tingvold <joachim@tingvold.com>
Message-ID: <20110625024533.GA86406@nargothrond.kdm.org>
References: <20110208201310.GA97635@nargothrond.kdm.org>
<4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com>
<20110218171619.GB78796@nargothrond.kdm.org>
<318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com>
<20110221155041.GA37922@nargothrond.kdm.org>
<3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com>
<20110221214544.GA43886@nargothrond.kdm.org>
<2E532F21-B969-4216-9765-BC1CC1EAB522@tingvold.com>
<20110225183351.GA31590@nargothrond.kdm.org>
<8AFCE2C0-A87D-414B-912F-C80C158B6D94@tingvold.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8AFCE2C0-A87D-414B-912F-C80C158B6D94@tingvold.com>
User-Agent: Mutt/1.4.2i
Cc: freebsd-scsi@freebsd.org, Alexander Motin <mav@freebsd.org>
Subject: Re: mps0-troubles
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 03:07:50 -0000
On Sat, Jun 25, 2011 at 03:30:37 +0200, Joachim Tingvold wrote:
> On Fri, Feb 25, 2011, at 19:33:51PM GMT+01:00, Kenneth D. Merry wrote:
> >I just checked the change into -current, I'll merge it to -stable
> >next week.
>
> I'm back! Missed me? :-D
>
> After running fine for a while, I decided to do some more testing.
> Usual 'dd' in a while-loop over the night, and woke up to this;
>
> ###
> mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
> mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
> mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
> mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 65536
> mps0: (0:39:0) terminated ioc 804b scsi 0 state c xfer 0
> mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
> mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
> mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
> mps0: (0:39:0) terminated ioc 804b scsi 0 state 0 xfer 0
> mps0: mpssas_remove_complete on target 0x0027, IOCStatus= 0x0
> (da7:mps0:0:39:0): lost device
> (da7:mps0:0:39:0): Invalidating pack
> (da7:mps0:0:39:0): Invalidating pack
> (da7:mps0:0:39:0): Invalidating pack
> (da7:mps0:0:39:0): Invalidating pack
> (da7:mps0:0:39:0): Synchronize cache failed, status == 0xa, scsi
> status == 0x0
> (da7:mps0:0:39:0): removing device entry
> da7 at mps0 bus 0 scbus0 target 39 lun 0
> da7: <ATA WDC WD10EACS-00Z 1B01> Fixed Direct Access SCSI-5 device
> da7: 300.000MB/s transfers
> da7: Command Queueing enabled
> da7: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
> ###
>
> Now, the disk was present at the time I checked, as camcontrol confirms;
>
> [root@filserver /storage/tmp]# camcontrol devlist|grep da7
> <ATA WDC WD10EACS-00Z 1B01> at scbus0 target 39 lun 0 (pass8,da7)
Yep, this looks like what I've seen with mps controllers talking to SATA
drives through an expander under high load.
I know I've asked this before, but what brand of expander do you have, and
is it 3Gb or 6Gb? It looks like the drive is probing at 3Gb in any case.
It looks like the drive went away and came back.
> However, the disk was marked as "REMOVED" by 'zpool status';
>
> ###
> [jocke@filserver /storage/tmp]$ zpool status
> pool: storage
> state: DEGRADED
>
> NAME STATE READ WRITE CKSUM
> storage DEGRADED 0 0 0
> raidz2-0 ONLINE 0 0 0
> da8 ONLINE 0 0 0
> da9 ONLINE 0 0 0
> da10 ONLINE 0 0 0
> da11 ONLINE 0 0 0
> da15 ONLINE 0 0 0
> da16 ONLINE 0 0 0
> raidz2-1 DEGRADED 0 0 0
> da0 ONLINE 0 0 0
> da1 ONLINE 0 0 0
> da2 ONLINE 0 0 0
> da3 ONLINE 0 0 0
> da4 ONLINE 0 0 0
> da5 ONLINE 0 0 0
> da6 ONLINE 0 0 0
> da7 REMOVED 0 0 0
> da12 ONLINE 0 0 0
> da13 ONLINE 0 0 0
> spares
> da14 AVAIL
> ###
>
> A quick 'zpool online storage da7' works fine, as suspected, and pool
> is resilvering at the moment.
>
> I find it a bit worrisome that a disk was removed like that. It
> _could_ be that the disk isn't completely good, however, due to my
> previous experiences with mps, I suspect the disk is fine (smartctl-
> readouts on the disk seems to be good as well).
The disk is probably fine. That error tends to happen when you have a lot
of contention under high load. I wish I knew why. It is something that
LSI should fix, I was talking to them for a while trying to get an answer
on it, but got nowhere.
With some of the ZFS improvements that Justin is working on in -current,
I think the drive would have probably been automatically put back into
the pool when it came back.
Ken
--
Kenneth Merry
ken@FreeBSD.ORG