From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 23 11:07:12 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 D0EEA1065672 for ; Mon, 23 Jan 2012 11:07:12 +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 B5D578FC1F for ; Mon, 23 Jan 2012 11:07:12 +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 q0NB7CrU081073 for ; Mon, 23 Jan 2012 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0NB7CpV081070 for freebsd-scsi@FreeBSD.org; Mon, 23 Jan 2012 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Jan 2012 11:07:12 GMT Message-Id: <201201231107.q0NB7CpV081070@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, 23 Jan 2012 11:07:13 -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/163812 scsi [mpt] problem with mpt driver for lsi controlled conne o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c f kern/163130 scsi [mpt] cannot dumpon to mpt connected disk 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 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 51 problems total. From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 25 11:33:51 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 1A2D91065679; Wed, 25 Jan 2012 11:33:51 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop03.sare.net (proxypop03.sare.net [194.30.0.207]) by mx1.freebsd.org (Postfix) with ESMTP id A795A8FC0C; Wed, 25 Jan 2012 11:33:50 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id 3ABAD9DC639; Wed, 25 Jan 2012 12:13:54 +0100 (CET) From: Borja Marcos Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jan 2012 12:13:53 +0100 Message-Id: <88146602-824A-47DD-B1EC-1F62BCF54389@sarenet.es> To: freebsd-scsi@freebsd.org, freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: Subject: To JBOD or just to pass, that is the question 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: Wed, 25 Jan 2012 11:33:51 -0000 =09 Hi Sorry for the cross-posting, but this pertains both filesystems and host = adapters. Since ZFS was added to FreeBSD it has collided with the standard = practice of server manufacturers: including "RAID" cards. ZFS is designed to control the disks directly, and RAID cards tend to = get in the middle, complicating things. Some cards do provide access to = disks, working as plain host adapters without more added features, as = they should be. But so far I have found two problematic cases: mfi and = aac cards.=20 Of course, the standard suggestion is to create a logical volume for = each disk, so that you have the rough equivalent of a hard disk attached = to a host adapter. However, it has its drawbacks: - Added layer of complexity. At least with mfi cards, replacing a broken = disk involves a bit of device dependant voodoo incantations. It should = be a matter of physically replacing the disk and maybe do a camcontrol = rescan, nothing else.=20 - Are such volume-per-disk transportable from one controller to another? = What happens if I need to install them on a different machine with a = different host adapter? ZFS provides that interoperability, but the RAID = cards can be a problem. - More complexity: What's, for instance, the caching behavior of the = RAID card? ZFS decides when to flush, not to flush, etc. Battery backed = RAID cards show (as far as I know) a configuration dependent caching, = maybe ignoring commands received from the OS storage subsystem? At least = there's no detailed documentation as far as I know. So I tend to dislike = that "firmware in the middle". Long ago I asked for help on freebsd-scsi and Scott Long sent a simple = patch to make hard disks shown as pass-through devices available to the = "da" driver, hence becoming real hard disks. It's just a matter of = deleting all the logical volumes before using the disks. I've been = running this on a machine with MFI since 2007 and so far so good. The = machine is now on 8.1 and I hope to update to 9 soon. The freebsd-scsi thread: = http://lists.freebsd.org/pipermail/freebsd-scsi/2007-October/003224.html The behavior with my torture tests was good. One of the things I use to = do when testing a configuration is to remove a disk suddenly with the = system working. That was a pain in the ass with the mfi thingy, really = straightforward with the disks accessed in pass through mode. Now I am installing a Sun X4240 server, and, surprisingly, I've stumbled = upon a similar problem. Now it's an "aac" card: aac0: mem 0xdfe00000-0xdfffffff irq 17 at device 0.0 = on pci4 aac0: Enabling 64-bit address support aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0: Sun STK RAID INT, aac driver 2.1.9-1 aacp0: on aac0 aacp1: on aac0 aacp2: on aac0 This is a disk on /var/run/dmesg.boot, da0: Fixed Direct Access SCSI-5 device=20= da0: 0KB/s transfers da0: 140009MB (286739329 512 byte sectors: 255H 63S/T 17848C) and this is what I see from camcontrol: # camcontrol devlist at scbus6 target 8 lun 0 (da0,pass0) at scbus6 target 9 lun 0 (da1,pass1) at scbus6 target 10 lun 0 (da2,pass2) at scbus6 target 11 lun 0 (da3,pass3) at scbus6 target 12 lun 0 (da4,pass4) at scbus6 target 13 lun 0 (da5,pass5) at scbus6 target 14 lun 0 (da6,pass6) at scbus6 target 15 lun 0 (da7,pass7) at scbus6 target 16 lun 0 (da8,pass8) at scbus6 target 17 lun 0 (da9,pass9) at scbus6 target 18 lun 0 = (da10,pass10) at scbus6 target 19 lun 0 = (da11,pass11) at scbus6 target 20 lun 0 = (da12,pass12) at scbus6 target 21 lun 0 = (da13,pass13) at scbus6 target 22 lun 0 = (da14,pass14) at scbus6 target 23 lun 0 = (da15,pass15) at scbus8 target 0 lun 0 = (ses0,pass16) at scbus8 target 1 lun 0 = (ses1,pass17) at scbus8 target 2 lun 0 = (ses2,pass18) at scbus15 target 0 lun 0 = (cd0,pass19) at scbus16 target 0 lun 0 = (da16,pass20) camcontrol inq 6:8:0 pass0: Fixed Direct Access SCSI-5 device pass0: Serial Number 000946821D70 3SD21D70 pass0: 3.300MB/s transfers=20 The transfer speed seems to be silly, but Bonnie++ on a 16 disk raidz2 = gave 200+MBps block writing, 700+MBps block reading, so it seems to be = working. So far there's just one side effect of accessing the disks in pass = through mode: I cannot reboot the machine, seems to hang after flushing = the buffers. It happens both with the mfi and the aac drivers. Just wondering, should we have, maybe, a tunable allowing aac and mfi to = bypass the RAID firmware thingy? Is there any kind of exhaustive test we = could perform to make sure that the card isn't doing weird things. I've noticed, in the case of the aac machine I'm testing, that = camcontrol tags shows just one "device opening". I'm wondering if it = would be safe to increase them? Right now the machine isn't in = production, so I can perform some tests. Best regards, Borja. From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 26 04:47:41 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 0D111106564A; Thu, 26 Jan 2012 04:47:41 +0000 (UTC) (envelope-from freebsd@penx.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) by mx1.freebsd.org (Postfix) with ESMTP id C187D8FC12; Thu, 26 Jan 2012 04:47:40 +0000 (UTC) Received: from [IPv6:::1] (localhost [IPv6:::1]) by btw.pki2.com (8.14.5/8.14.5) with ESMTP id q0Q4lbB9022991; Wed, 25 Jan 2012 20:47:37 -0800 (PST) (envelope-from freebsd@penx.com) From: Dennis Glatting To: "Kenneth D. Merry" In-Reply-To: <20120120204459.GA51162@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> Content-Type: text/plain; charset="us-ascii" Date: Wed, 25 Jan 2012 20:47:37 -0800 Message-ID: <1327553257.19745.6.camel@btw.pki2.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: q0Q4lbB9022991 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: freebsd@penx.com Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available 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, 26 Jan 2012 04:47:41 -0000 On Fri, 2012-01-20 at 13:44 -0700, Kenneth D. Merry wrote: > The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > HBAs as well as WarpDrive controllers, is available here: > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > I plan to check it in to head next week, and then MFC it into stable/9 a > week after that most likely. > > Please test it out and let me know if you run into any problems. > > In addition to supporting WarpDrive, the driver also supports Integrated > RAID. > > Thanks to LSI for doing the work on this driver! > Does this include the SAS2008 series chips? I have two systems, one a Tyan FT48-B8812 with a S8812 MB and Interlagos chips, where I am interested in using a driver under 9.0 amd64. > I have added a number of other infrastructure changes that are necessary > for the driver, and here is a brief summary: > > - A new Advanced Information buffer is now added to the EDT for drives > that support READ CAPACITY (16). The da(4) driver updates this buffer > when it grabs new read capacity data from a drive. > - The mps(4) driver will look for Advanced Information state change async > events, and updates its table of drives with protection information > turned on accordingly. > - The size of struct scsi_read_capacity_data_long has been bumped up to > the amount specified in the latest SBC-3 draft. The hope is to avoid > some future structure size bumps with that change. The API for > scsi_read_capacity_16() has been changed to add a length argument. > Hopefully this will future-proof it somewhat. > - __FreeBSD_version bumped for the addition of the Advanced Information > buffer with the read capacity information. The mps(4) driver has a > kludgy way of getting the information on versions of FreeBSD without > this change. > > I believe that the CAM API changes are mild enough and beneficial enough > for a merge into stable/9, but they are intertwined with the unmap changes > in the da(4) driver, so those changes will have to go back to stable/9 as > well in order to MFC the full set of changes. > > Otherwise it'll just be the driver that gets merged into stable/9, and > it'll use the kludgy method of getting the read capacity data for each > drive. > > A couple of notes about issues with this driver: > > - Unlike the current mps(4) driver, it probes sequentially. If you have a > lot of drives in your system, it will take a while to probe them all. > - You may see warning messages like this: > > _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste > nt table because there is no free space available > _mapping_add_new_device: failed to add the device with handle 0x001a to persiste > nt table because there is no free space available > > - The driver is not endian safe. (It assumes a little endian machine.) > This is not new, the driver in the tree has the same issue. > > The LSI folks know about these issues. The driver has passed their testing > process. > > Many thanks to LSI for going through the effort to support FreeBSD. > > Ken From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 26 04:54:10 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 3B0251065679; Thu, 26 Jan 2012 04:54:10 +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 E98D08FC18; Thu, 26 Jan 2012 04:54:09 +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 q0Q4s9NY090929; Wed, 25 Jan 2012 21:54:09 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q0Q4s9i7090928; Wed, 25 Jan 2012 21:54:09 -0700 (MST) (envelope-from ken) Date: Wed, 25 Jan 2012 21:54:09 -0700 From: "Kenneth D. Merry" To: Dennis Glatting Message-ID: <20120126045409.GA90912@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> <1327553257.19745.6.camel@btw.pki2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1327553257.19745.6.camel@btw.pki2.com> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: LSI supported mps(4) driver available 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, 26 Jan 2012 04:54:10 -0000 On Wed, Jan 25, 2012 at 20:47:37 -0800, Dennis Glatting wrote: > On Fri, 2012-01-20 at 13:44 -0700, Kenneth D. Merry wrote: > > The LSI-supported version of the mps(4) driver that supports their 6Gb SAS > > HBAs as well as WarpDrive controllers, is available here: > > > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > > > I plan to check it in to head next week, and then MFC it into stable/9 a > > week after that most likely. > > > > Please test it out and let me know if you run into any problems. > > > > In addition to supporting WarpDrive, the driver also supports Integrated > > RAID. > > > > Thanks to LSI for doing the work on this driver! > > > > Does this include the SAS2008 series chips? I have two systems, one a > Tyan FT48-B8812 with a S8812 MB and Interlagos chips, where I am > interested in using a driver under 9.0 amd64. Yes. The driver in 9.0 supports the 2008 as well. Ken -- Kenneth Merry ken@FreeBSD.ORG