From owner-freebsd-scsi@FreeBSD.ORG Mon May 30 11:07:07 2011 Return-Path: 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 632B9106567C for ; Mon, 30 May 2011 11:07:07 +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 48F458FC2E for ; Mon, 30 May 2011 11:07:07 +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 p4UB77bn050496 for ; Mon, 30 May 2011 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4UB76tl050494 for freebsd-scsi@FreeBSD.org; Mon, 30 May 2011 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 May 2011 11:07:06 GMT Message-Id: <201105301107.p4UB76tl050494@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 11:07:07 -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/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after 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 45 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon May 30 20:39:00 2011 Return-Path: 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 C3E80106564A for ; Mon, 30 May 2011 20:39:00 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 812BD8FC0C for ; Mon, 30 May 2011 20:39:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id A009E50852 for ; Mon, 30 May 2011 21:38:59 +0100 (BST) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afdbmKZIH1Fl for ; Mon, 30 May 2011 21:38:59 +0100 (BST) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 216CA50830 for ; Mon, 30 May 2011 21:38:59 +0100 (BST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Dan Langille In-Reply-To: Date: Mon, 30 May 2011 16:38:57 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <0D43CD5E-89F7-4A1C-A0C3-6DBA8039F367@langille.org> References: To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.1084) Subject: Re: Does the tape library need cleaning? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 20:39:00 -0000 On May 28, 2011, at 6:03 PM, Dan Langille wrote: > I'm wondering if there is a way to query my tape library to see if = cleaning is required? This information is shown on the display of the = unit, but I'd like to query the device and display it on a webpage. >=20 > Here is what I have. >=20 > $ mtx -f /dev/pass11 inquiry > Product Type: Medium Changer > Vendor ID: 'DEC ' > Product ID: 'TL800 (C) DEC' > Revision: '0326' > Attached Changer API: No >=20 > I'm guessing I need to know more about about the scsi commands I can = send to the device and use camcontrol to extract the information. Much = like this command pulls back data (as extracted from a a: >=20 >=20 > set -- `camcontrol cmd $tape -v -t 3 -c "4d 0 43 0 0 0 0 0 40 0" -i = 64 \ Reading = http://support.gateway.com/s/Manuals/servers/quantum_7000_product_manual.p= df shows me that cleaning status detection is possible. I started by understanding what my script (provided by a third partty) = does. Based on my script, I know that 43 is read statistics (as opposed to 42 = which is write statistics). So far, I've learned a bit about CDB and know that 4d =3D 'LOG SENSE'. According to 5.4.8 LOG SENSE (4Dh), the third parameter, 43, seems to be = the PC and Page Code. 43 =3D 0100 0101 * The 4 specifies cumulative values (see figure 5-20 LOG Page Control = Definitions) * The 3 specifies Last n Errors Events Page ( see figure 5-21 LOG SENSE = Pages Supported) Does this make sense to anyone else? Section 5.4.8.6 Device Status Log Sense Page (3Eh) seems to have what I = need. Particularly: * parameter code (0001h) * ASC 80h ASCQ 01h =3D=3D Cleaning Required It is at this point that I start getting confused about what camcontrol = command I should use. I don't know how to incorporate 3E into the camcontrol command. It = seems that 4D is the key.... I'm confused... > "{skip} *i4 \ > {skip} *i4 \ > {Corrected errors with substantial delay } i4 \ > {skip} *i4 \ > {Corrected errors with possible delay } i4 \ > {skip} *i4 \ > {Total errors } i4 \ > {skip} *i4 \ > {Total errors corrected } i4 \ > {skip} *i4 \ > {Total times correction algorithm processed} i4 \ > {skip} *i4 \ > {Total bytes processed } i2 i3 i3 \ > {skip} *i4 \ > {Total uncorrected errors } i4" The above output is related to Table 5-18 on page 114. > ` > echo " Corrected errors with substantial delay: $1" > echo " Corrected errors with possible delay : $2" > echo " Total errors : $3" > echo " Total errors corrected : $4" > echo " Total times correction algorithm used : $5" > tmp=3D`echo "($6 * 16777216 + $7) * 16777216 + $8" | bc` > echo " Total bytes processed : $tmp" --=20 Dan Langille - http://langille.org From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 2 12:58:49 2011 Return-Path: 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 9FEC6106566B for ; Thu, 2 Jun 2011 12:58:49 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norman-vivat.ru [89.250.210.68]) by mx1.freebsd.org (Postfix) with ESMTP id ED2958FC16 for ; Thu, 2 Jun 2011 12:58:48 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::7cb]) by elf.hq.norma.perm.ru (8.14.4/8.14.4) with ESMTP id p52CioKO027588 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 2 Jun 2011 18:44:50 +0600 (YEKST) (envelope-from eugene@zhegan.in) Message-ID: <4DE785C2.6080205@zhegan.in> Date: Thu, 02 Jun 2011 18:44:50 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.15) Gecko/20110325 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Thu, 02 Jun 2011 18:44:50 +0600 (YEKST) X-Callback: Sender verified by milter-callback 1.5.14 at elf.hq.norma.perm.ru. X-Callback-Status: relay [] found in white list. X-Callback-Envelope-From: eugene@zhegan.in X-Spam-Status: No hits=0.8 bayes=0.5 testhits RDNS_NONE=0.793 autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on elf.hq.norma.perm.ru Subject: lsi1064e X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 12:58:49 -0000 Hi. I'm using FreeBSD 8.2 and IBM system x 3250 servers which are bundled with an onboard LSI 1064e controller. I'm using 'em with geom_mirror and zfs (I have like dozen of these). Last time I noticed weird thing on a server with gmirror: one drive died and the server hung up until it was rebooted. This week I was examining some zfs-related freezes (I guess its about arc size, but someone on the irc told me that disks timeouts can be the reason too) and I was experimenting on my test server (waiting for being put into the production). And I noticed some wrong (at least I think it's wrong) behaviour: keeping in mind that last time I got freeze when drive died, I pulled out one of two drives in a zfs mirrored pool. Then I got immediate freeze - all of the disk operations were freezed, but the system was alive. I entered the kernel debugger and saw a bunch of proccesses in D state, including some of the zfs threads. I updated the LSI1064e firmware (last 1.30.xx found on the IBM site), the BIOS, but nothing helps. When one of the disks is pulled out (there's no need to do that in production, but I guess the exact same thing happens when the drive dies along with all of its electric circuits) the system waits indefinitely, until the drive is pushed back, or until the server is rebooted. Then (if the drive is pushed back) the mpt driver realises that either the drive was reset, or that device was lost (I don't know what this depends from). Funny thing: after the drive is pulled out and pushed back, and the camcontrol rescan is issued, you can pull it out again, and this time (and any time after that) the system willl detect that drive is gone quite fast, and no disk operations freeze will happen. You can imagine that this behaviour is not the one anyone expects when drive dies. So I want to ask - if this, perhaps, can be tuned, so the system will keep running and somehow will detect that the drive is failed in some short time, like 3-15 seconds ? Or is this a bug and I need to write a pr ? Thanks. Eugene.