From owner-freebsd-scsi@FreeBSD.ORG Mon May 7 11:07:21 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6E66106564A for ; Mon, 7 May 2012 11:07:21 +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 D09878FC17 for ; Mon, 7 May 2012 11:07:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q47B7LE1072494 for ; Mon, 7 May 2012 11:07:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q47B7L1a072492 for freebsd-scsi@FreeBSD.org; Mon, 7 May 2012 11:07:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 May 2012 11:07:21 GMT Message-Id: <201205071107.q47B7L1a072492@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, 07 May 2012 11:07:22 -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/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err 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/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/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 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 50 problems total. From owner-freebsd-scsi@FreeBSD.ORG Thu May 10 14:31:06 2012 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 642F6106566B for ; Thu, 10 May 2012 14:31:06 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id 3ECDE8FC25 for ; Thu, 10 May 2012 14:31:06 +0000 (UTC) Received: from EXHUB03.exchhosting.com (192.168.11.104) by exhub05.exchhosting.com (192.168.11.101) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 10 May 2012 07:31:04 -0700 Received: from EXMBX10.exchhosting.com ([fe80::9c37:32f6:a508:a44f]) by EXHUB03.exchhosting.com ([fe80::ac41:fbe5:3959:ad64%12]) with mapi; Thu, 10 May 2012 07:31:03 -0700 From: Trent Nelson To: "mj@feral.com" Date: Thu, 10 May 2012 07:31:01 -0700 Thread-Topic: isp target mode bugs? (was Re: Missing sysctl options for isp driver) Thread-Index: Ac0uuYb89rCSl2HrSzmwEidz+gE+hw== Message-ID: <079A4619-38CC-443D-A191-3481819BEBB8@snakebite.org> References: <20120502203948.GA1141@snakebite.org> <4FA1DF1C.2030706@feral.com> <20120503050956.GA18983@snakebite.org> <4FA28976.2070607@feral.com> In-Reply-To: <4FA28976.2070607@feral.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" Subject: isp target mode bugs? (was Re: Missing sysctl options for isp driver) 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, 10 May 2012 14:31:06 -0000 > > > FreeBSD is the most up to date, but certainly has bugs in target mode= .=20 > > I, uh, I don't think I'm using target mode. I've got four Xyratex RS-= =20 > > 1600-FC2 JBODs (16x146GB + 48x36GB) connected to two-but-soon-to-be-fou= r > > HP StorageWorks SAN Switch 2/16s. Each FreeBSD box has a minimum of tw= o > > FC HBA ports; each HBA port goes to a different switch, and zoning conf= ig > > on the switches controls which disks each hosts sees (although more on > > this later). > > So, uh, I think that constitutes fabric mode right? The switch reports > Target Mode is where the FreeBSD box can pretend to be a disk. Yes, > that's fabric. I disregarded target mode when I read your explanation, thinking it wasn't relevant to my environment. However, it dawned on me this morning how useful this could be. Every box on my network has a minimum of two FC HBAs, and they're all capable of booting from an FC drive. Other than the amd64 FreeBSD boxes, every= - thing else is non-PC (SPARC, IA64, Power4+, PA-RISC etc). Having had an absolutely woeful experience with the Mylex FFx2 RAID=20 controller intended for the Xyratex enclosures, I've since decided to ditch it an leverage ZFS + JBOD instead. However, it's been bothering me a little bit that all the non-ZFS hosts wouldn't benefit from, er, ZFS. I'd have to set up mirrored root volum= es and all that crap to get a similar level of redundancy, but I'd be miss= ing all the ZFS Good Stuff. I was planning on leveraging iSCSI (via zfs volumes), which would allow= me to export ZFS-backed disks to non-ZFS hosts, but I'd really be only abl= e to use those volumes for (non-important) data -- I couldn't boot off th= em nor have them as primary OS disks (limitation of old-ish hardware). As every box on the network has two FC HBAs, I found myself thinking th= is morning how useful it would be if I could present zfs volumes as disks = to the SAN fabric, then zone/allocate them as if they were JBODs. ....ergo, target mode! =20 Which makes your comment below all the more interesting: > > > FreeBSD is the most up to date, but certainly has bugs in target mode= .=20 What sort of bugs are we talking about? ;-) =20 I'm pretty keen to explore this route after this morning's revelation. = I could boot all my AIX/HP-UX/etc boxes off ZFS-backed volumes; which mea= ns I could snapshot, clone, rollback, compress, dedup etc behind the scene= s. Which would be absolutely bad-ass. What are your thoughts on this? Viable option or are there fundamental= , insurmountable technical issues that'll make my life miserable? Trent. 56,1 = Bot From owner-freebsd-scsi@FreeBSD.ORG Sat May 12 00:11:05 2012 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 3F2E7106564A for ; Sat, 12 May 2012 00:11:05 +0000 (UTC) (envelope-from Terence_Telkamp@DELL.com) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) by mx1.freebsd.org (Postfix) with ESMTP id F38BC8FC0A for ; Sat, 12 May 2012 00:11:04 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.75,573,1330927200"; d="scan'208,217";a="530755573" Received: from mail.compellent.com ([64.238.244.148]) by aussmtpmrkps320.us.dell.com with ESMTP; 11 May 2012 19:09:57 -0500 From: Terence Telkamp To: "freebsd-scsi@freebsd.org" Date: Fri, 11 May 2012 19:09:55 -0500 Thread-Topic: Problem with Removable Disk Device on FreeBSD Thread-Index: Ac0vz39AMuKI+8hhSLiJM/i8HePbxw== Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA03E75B33D9@shandy.Beer.Town> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: John Partridge Subject: Problem with Removable Disk Device on FreeBSD 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: Sat, 12 May 2012 00:11:05 -0000 Hello, I am having trouble using an RD1000 device with FreeBSD 8.1 and 9.0. The R= D1000 that I'm using is a device that has a removable SATA disk cartridge a= nd connects to a host system through USB. There are other similar devices = out there such as the RDX: http://www.imation.com/en-US/Scalable-Storage/Scalable-Storage-Products/RDX= -Removable-Hard-Disk-Storage/RDX-Removable-HDD-Storage-System-USB-30/ My problem is that FreeBSD does not recognize when the cartridge is inserte= d or ejected from the device. If I attach the RD1000 to the host with a ca= rtridge already inserted a dev node entry shows up (e.g. da0) as well as a = slice entry (e.g. da0s1), but the slice entry does not go away after I ejec= t the cartridge. Conversely, if I attach the RD1000 that doesn't have a ca= rtridge inserted, a dev node entry for the device shows up (e.g. da0), but = no slice entery shows up. Inserting a cartridge after the RD1000 has alrea= dy been attached still does not cause the slice entry that I expect to show= up. No dmesg shows up to indicate that anything has changed when the cart= ridge is inserted or ejected after the device has alread been attached. Do= ing a camcontrol rescan had no effect on FreeBSD recogizing if there is a = cartridge inserted in the RD1000 or not. Searching the internet, I found that people have run into similar issue usi= ng zip drives. They were able to work around the issue by redirecting a tr= ue command to the device (e.g. true > da0). After doing that FreeBSD will = recognize an inserted cartridge in the RD1000 and create a dev slice entry = for it. However, that doesn't help me recognize eject events. Also, I wou= ld like to understand the root cause and hopefully find a more direct solut= ion instead of just a workaround. I've experimented with hosts running other other operating systems. Both L= inux and Windows hosts respond to the insertion and removal of the cartridg= e. I tried the version of the RD1000 that connects to the host through a SATA = port and saw similar results. If I booted with a cartridge already inserte= d in the RD1000 I would get an afd dev entry, but if I booted without a car= tridge inserted the afd entry would not be present. Inserting or ejecting = the cartridge after boot would have no effect. Doing an atacontrol detac= h would cause the afd dev entry to disappear whether the cartridge was inse= rted or not. Doing a subsequent atacontrol attach would cause the afd entr= y to reappear only if a cartridge was inserted. Since the behavior is simi= lar whether the RD1000 is attached through USB or SATA, I am wondering if t= here is a problem in the CAM or SCSI layers of FreeBSD. Does anybody have any ideas on how I can narrow this issue down further? Terence Telkamp Storage Development Associate Engineer II Dell | Compellent