From owner-freebsd-scsi@freebsd.org Mon Aug 24 21:24:25 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A01179C206F for ; Mon, 24 Aug 2015 21:24:25 +0000 (UTC) (envelope-from dan@langille.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8632AAF for ; Mon, 24 Aug 2015 21:24:25 +0000 (UTC) (envelope-from dan@langille.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8336E9C206E; Mon, 24 Aug 2015 21:24:25 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 829B89C206C; Mon, 24 Aug 2015 21:24:25 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin2.langille.org (clavin2.langille.org [199.233.228.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "clavin.langille.org", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42BA7AE; Mon, 24 Aug 2015 21:24:25 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin2.int.langille.org (clavin2.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id 288F43D0B ; Mon, 24 Aug 2015 21:24:23 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: sa(4) driver changes available for test From: Dan Langille In-Reply-To: <20150302172629.GA87055@mithlond.kdm.org> Date: Mon, 24 Aug 2015 17:24:22 -0400 Cc: scsi@freebsd.org, current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150214003232.GA63990@mithlond.kdm.org> <4A478C5C-7965-498E-9F0F-80192265E310@langille.org> <20150302001833.GA71528@mithlond.kdm.org> <6C82281F-649A-4DA8-8ACF-17E81C04F730@langille.org> <20150302003658.GA72258@mithlond.kdm.org> <20150302020608.GA73433@mithlond.kdm.org> <30C55F00-2DE4-4596-96EA-2E3CC40B4DB6@langille.org> <20150302172629.GA87055@mithlond.kdm.org> To: "Kenneth D. Merry" X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2015 21:24:25 -0000 > On Mar 2, 2015, at 12:26 PM, Kenneth D. Merry wrote: >=20 > On Mon, Mar 02, 2015 at 11:43:15 -0500, Dan Langille wrote: >>=20 >>> On Mar 1, 2015, at 9:06 PM, Kenneth D. Merry = wrote: >>>=20 >>> On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: >>>>=20 >>>>> On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry = wrote: >>>>>=20 >>>>> On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: >>>>>>=20 >>>>>>> On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry = wrote: >>>>>>>=20 >>>>>>> On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: >>>>>>>>=20 >>>>>>>>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry = wrote: >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> I have a fairly large set of changes to the sa(4) driver and = mt(1) driver >>>>>>>>> that I'm planning to commit in the near future. >>>>>>>>>=20 >>>>>>>>> A description of the changes is here and below in this = message. >>>>>>>>>=20 >>>>>>>>> If you have tape hardware and the inclination, I'd appreciate = testing and >>>>>>>>> feedback. >>>>>>>>>=20 >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>> Rough draft commit message: >>>>>>>>>=20 >>>>>>>>> = http://people.freebsd.org/~ken/sa_changes_commitmsg.20150213.3.txt >>>>>>>>>=20 >>>>>>>>> The patches against FreeBSD/head as of SVN revision 278706: >>>>>>>>>=20 >>>>>>>>> http://people.freebsd.org/~ken/sa_changes.20150213.3.txt >>>>>>>>>=20 >>>>>>>>> And (untested) patches against FreeBSD stable/10 as of SVN = revision 278721. >>>>>>>>>=20 >>>>>>>>> = http://people.freebsd.org/~ken/sa_changes.stable_10.20150213.3.txt >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>>=20 >>>>>>>>> The intent is to get the tape infrastructure more up to date, = so we can >>>>>>>>> support LTFS and more modern tape drives: >>>>>>>>>=20 >>>>>>>>> http://www.ibm.com/systems/storage/tape/ltfs/ >>>>>>>>>=20 >>>>>>>>> I have ported IBM's LTFS Single Drive Edition to FreeBSD. The = port depends >>>>>>>>> on the patches linked above. It isn't fully cleaned up and = ready for >>>>>>>>> redistribution. If you're interested, though, let me know and = I'll tell >>>>>>>>> you when it is ready to go out. You need an IBM LTO-5, LTO-6, = TS1140 or >>>>>>>>> TS1150 tape drive. HP drives aren't supported by IBM's LTFS, = and older >>>>>>>>> drives don't have the necessary features to support LTFS. >>>>>>>>>=20 >>>>>>>>> The commit message below outlines most of the changes. >>>>>>>>>=20 >>>>>>>>> A few comments: >>>>>>>>>=20 >>>>>>>>> 1. I'm planning to commit the XPT_DEV_ADVINFO changes = separately. >>>>>>>>>=20 >>>>>>>>> 2. The XML output is similar to what GEOM and CTL do. It = would be nice to >>>>>>>>> figure out how to put a standard schema on it so that standard = tools >>>>>>>>> could read it. I don't know how feasible that is, since I = haven't >>>>>>>>> time to dig into it. If anyone has suggestions on whether = that is >>>>>>>>> feasible or advisable, I'd appreciate feedback. >>>>>>>>>=20 >>>>>>>>> 3. I have tested with a reasonable amount of tape hardware = (see below for a >>>>>>>>> list), but more testing and feedback would be good. >>>>>>>>>=20 >>>>>>>>> 4. Standard 'mt status' output looks like this: >>>>>>>>>=20 >>>>>>>>> # mt -f /dev/nsa3 status -v >>>>>>>>> Drive: sa3: Serial Number: 101500520A >>>>>>>>> --------------------------------- >>>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>>> Current: 0x5a:LTO-6 variable 384607 enabled = (0xff) >>>>>>>>> --------------------------------- >>>>>>>>> Current Driver State: at rest. >>>>>>>>> --------------------------------- >>>>>>>>> Partition: 0 Calc File Number: 0 Calc Record = Number: 0 >>>>>>>>> Residual: 0 Reported File Number: 0 Reported Record = Number: 0 >>>>>>>>> Flags: BOP >>>>>>>>>=20 >>>>>>>>> 5. 'mt status -v' looks like this: >>>>>>>>>=20 >>>>>>>>> # mt -f /dev/nsa3 status -v >>>>>>>>> Drive: sa3: Serial Number: 101500520A >>>>>>>>> --------------------------------- >>>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>>> Current: 0x5a:LTO-6 variable 384607 enabled = (0xff) >>>>>>>>> --------------------------------- >>>>>>>>> Current Driver State: at rest. >>>>>>>>> --------------------------------- >>>>>>>>> Partition: 0 Calc File Number: 0 Calc Record = Number: 0 >>>>>>>>> Residual: 0 Reported File Number: 0 Reported Record = Number: 0 >>>>>>>>> Flags: BOP >>>>>>>>> --------------------------------- >>>>>>>>> Tape I/O parameters: >>>>>>>>> Maximum I/O size allowed by driver and controller (maxio): = 1081344 bytes >>>>>>>>> Maximum I/O size reported by controller (cpi_maxio): 5197824 = bytes >>>>>>>>> Maximum block size supported by tape drive and media = (max_blk): 8388608 bytes >>>>>>>>> Minimum block size supported by tape drive and media = (min_blk): 1 bytes >>>>>>>>> Block granularity supported by tape drive and media = (blk_gran): 0 bytes >>>>>>>>> Maximum possible I/O size (max_effective_iosize): 1081344 = bytes >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> # mtx -f /dev/pass0 status >>>>>>>> Storage Changer /dev/pass0:2 Drives, 10 Slots ( 0 Import/Export = ) >>>>>>>> Data Transfer Element 0:Empty >>>>>>>> Data Transfer Element 1:Empty >>>>>>>> Storage Element 1:Empty >>>>>>>> Storage Element 2:Empty >>>>>>>> Storage Element 3:Empty >>>>>>>> Storage Element 4:Full :VolumeTag=3DFAI260 = =20 >>>>>>>> Storage Element 5:Full :VolumeTag=3DFAI261 = =20 >>>>>>>> Storage Element 6:Full :VolumeTag=3DFAI262 = =20 >>>>>>>> Storage Element 7:Full :VolumeTag=3DFAI263 = =20 >>>>>>>> Storage Element 8:Empty >>>>>>>> Storage Element 9:Empty >>>>>>>> Storage Element 10:Empty >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> It was at this point I spent the next 90 minute trying to get = the tape=20 >>>>>>>> drive out of the tape library to free a stuck tape. Some of = this was spent >>>>>>>> attempting, and failing, to undo a stripped screw. I stopped = the attempt when >>>>>>>> I noticed the screw did need to be removed. :/ >>>>>>>=20 >>>>>>> Thanks for all of the effort! Looks like it is paying off! :) >>>>>>>=20 >>>>>>>> When I do this command, I hear the drive move a bit, to read = the tape: >>>>>>>>=20 >>>>>>>> # mt -f /dev/nsa1 status >>>>>>>> Drive: sa1: Serial Number: = CXA09S1340 >>>>>>>> --------------------------------- >>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 = enabled (IDRC) >>>>>>>> --------------------------------- >>>>>>>> Current Driver State: at rest. >>>>>>>> --------------------------------- >>>>>>>> Partition: 0 Calc File Number: 0 Calc Record = Number: 0 >>>>>>>> Residual: 0 Reported File Number: -1 Reported Record = Number: -1 >>>>>>>> Flags: None >>>>>>>=20 >>>>>>> Looks like the drive isn't reporting position information. It = will still >>>>>>> be useful to try it with Bacula, though. >>>>>>>=20 >>>>>>>> # mt -f /dev/nsa1 ostatus =20 >>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> ---------available modes--------- >>>>>>>> 0: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 1: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 2: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 3: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> --------------------------------- >>>>>>>> Current Driver State: at rest. >>>>>>>> --------------------------------- >>>>>>>> File Number: 0 Record Number: 0 Residual Count 0 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> After doing a very small tar -c and tar -x, I have: >>>>>>>>=20 >>>>>>>> # mt -f /dev/nsa1 /dev/nsa1 ostatus >>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> ---------available modes--------- >>>>>>>> 0: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 1: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 2: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> 3: 0x1b:DLTapeIV(35GB) variable 85937 IDRC >>>>>>>> --------------------------------- >>>>>>>> Current Driver State: at rest. >>>>>>>> --------------------------------- >>>>>>>> File Number: 0 Record Number: 7 Residual Count 0 >>>>>>>=20 >>>>>>> Woohoo! It works. >>>>>>>=20 >>>>>>>> # mt -f /dev/nsa1 status -v >>>>>>>> Drive: sa1: Serial Number: = CXA09S1340 >>>>>>>> --------------------------------- >>>>>>>> Mode Density Blocksize bpi = Compression >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 = enabled (IDRC) >>>>>>>> --------------------------------- >>>>>>>> Current Driver State: at rest. >>>>>>>> --------------------------------- >>>>>>>> Partition: 0 Calc File Number: 0 Calc Record = Number: 7 >>>>>>>> Residual: 0 Reported File Number: -1 Reported Record = Number: -1 >>>>>>>> Flags: None >>>>>>>> --------------------------------- >>>>>>>> Tape I/O parameters: >>>>>>>> Maximum I/O size allowed by driver and controller (maxio): = 65536 bytes >>>>>>>> Maximum I/O size reported by controller (cpi_maxio): 0 bytes >>>>>>>> Maximum block size supported by tape drive and media (max_blk): = 16777214 bytes >>>>>>>> Minimum block size supported by tape drive and media (min_blk): = 2 bytes >>>>>>>> Block granularity supported by tape drive and media (blk_gran): = 0 bytes >>>>>>>> Maximum possible I/O size (max_effective_iosize): 65536 bytes >>>>>>>>=20 >>>>>>>> I may not get to testing Bacula today. =20 >>>>>>>>=20 >>>>>>>> Based on the above, is there any commands you'd like me to try? >>>>>>>=20 >>>>>>> Aside from making sure things work okay with Bacula, that is = probably >>>>>>> sufficient. These drives won't support density reports or = position >>>>>>> information. >>>>>>>=20 >>>>>>>> Read below regarding two tape drives >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> 6. Existing applications should work without changes. If not, = please let >>>>>>>>> me know. Hopefully they will move over time to the new = interfaces. >>>>>>>>>=20 >>>>>>>>> 7. There are lots of additional features that could be added = later. >>>>>>>>> Append-only support, encryption, more log pages, etc. >>>>>>>>>=20 >>>>>>>>> 8. I have SCSI READ ATTRIBUTE changes for camcontrol(8) that = will go in >>>>>>>>> separately. These changes allow displaying the contents of = the MAM >>>>>>>>> (Medium Auxiliary Memory) chips on LTO, TS and other modern = tape drives. >>>>>>>>> These are good, and a future possible direction is adding = attributes=20 >>>>>>>>> to the status XML from the sa(4) driver. >>>>>>>>>=20 >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>> Significant upgrades to sa(4) and mt(1). >>>>>>>>>=20 >>>>>>>>> The primary focus of these changes is to modernize FreeBSD's >>>>>>>>> tape infrastructure so that we can take advantage of some of = the >>>>>>>>> features of modern tape drives and allow support for LTFS. >>>>>>>>>=20 >>>>>>>>> Significant changes and new features include: >>>>>>>>>=20 >>>>>>>>> o sa(4) driver status and parameter information is now = exported via an >>>>>>>>> XML structure. This will allow for changes and improvements = later >>>>>>>>> on that will not break userland applications. The old = MTIOCGET >>>>>>>>> status ioctl remains, so applications using the existing = interface >>>>>>>>> will not break. >>>>>>>>>=20 >>>>>>>>> o 'mt status' now reports drive-reported tape position = information >>>>>>>>> as well as the previously available calculated tape position >>>>>>>>> information. These numbers will be different at times, = because >>>>>>>>> the drive-reported block numbers are relative to BOP = (Beginning >>>>>>>>> of Partition), but the block numbers calculated previously via >>>>>>>>> sa(4) (and still provided) are relative to the last filemark. >>>>>>>>> Both numbers are now provided. 'mt status' now also shows the >>>>>>>>> drive INQUIRY information, serial number and any position = flags >>>>>>>>> (BOP, EOT, etc.) provided with the tape position information. >>>>>>>>> 'mt status -v' adds information on the maximum possible I/O = size, >>>>>>>>> and the underlying values used to calculate it. >>>>>>>>>=20 >>>>>>>>> o The extra sa(4) /dev entries (/dev/saN.[0-3]) have been = removed. >>>>>>>>=20 >>>>>>>> How does this affect a tape library with more than one tape = drive? >>>>>>>>=20 >>>>>>>> [root@cuppy:~] # camcontrol amcontrol devlist >>>>>>>> at scbus0 target 0 lun 0 = (pass0,ch0) >>>>>>>> at scbus0 target 2 lun 0 = (sa1,pass2) >>>>>>>> at scbus1 target 0 lun 0 = (pass3,ada0) >>>>>>>> at scbus2 target 0 lun 0 = (pass4,ada1) >>>>>>>> at scbus3 target 0 lun 0 = (pass5,ses0) >>>>>>>>=20 >>>>>>>> This system has two tapes drives and I can access them through = the front panel but: >>>>>>>>=20 >>>>>>>> # ls -l /dev/*sa* >>>>>>>> crw-rw---- 1 root operator 0x65 Feb 28 22:04 /dev/esa1 >>>>>>>> crw-rw---- 1 root operator 0x64 Mar 1 22:43 /dev/nsa1 >>>>>>>> crw-rw---- 1 root operator 0x63 Feb 28 22:04 /dev/sa1 >>>>>>>> crw-rw---- 1 root operator 0x62 Feb 28 22:04 /dev/sa1.ctl >>>>>>>>=20 >>>>>>>> ... only one tape drives shows up. >>>>>>>=20 >>>>>>>=20 >>>>>>> Hmm. The tape drive is listed as sa1, which implies that there = may be an >>>>>>> sa0 that was there previously or is in the process of probing. = What does >>>>>>> dmesg show? How about 'camcontrol devlist -v'? >>>>>>=20 >>>>>> # camcontrol devlist -v >>>>>> scbus0 on ahc0 bus 0: >>>>>> at scbus0 target 0 lun 0 = (pass0,ch0) >>>>>> at scbus0 target 2 lun 0 = (sa1,pass2) >>>>>> <> at scbus0 target -1 lun = ffffffff () >>>>>> scbus1 on ahcich2 bus 0: >>>>>> at scbus1 target 0 lun 0 = (pass3,ada0) >>>>>> <> at scbus1 target -1 lun = ffffffff () >>>>>> scbus2 on ahcich4 bus 0: >>>>>> at scbus2 target 0 lun 0 = (pass4,ada1) >>>>>> <> at scbus2 target -1 lun = ffffffff () >>>>>> scbus3 on ahciem0 bus 0: >>>>>> at scbus3 target 0 lun 0 = (pass5,ses0) >>>>>> <> at scbus3 target -1 lun = ffffffff () >>>>>> scbus-1 on xpt0 bus 0: >>>>>> <> at scbus-1 target -1 lun = ffffffff (xpt0) >>>>>>=20 >>>>>>=20 >>>>>> BUT! >>>>>>=20 >>>>>> # grep sa /var/run/dmesg.boot=20 >>>>>> VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID >>>>>> module_register_init: MOD_LOAD (vesa, 0xffffffff80de3720, 0) = error 19 >>>>>> alc0: Using 1 MSIX message(s). >>>>>> isab0: at device 31.0 on pci0 >>>>>> isa0: on isab0 >>>>>> orm0: at iomem 0xce800-0xcefff on isa0 >>>>>> atkbdc0: at port 0x60,0x64 on isa0 >>>>>> sa0 at ahc0 bus 0 scbus0 target 1 lun 0 >>>>>> sa0: Removable Sequential Access = SCSI-2 device=20 >>>>>> sa0: Serial Number CXA22S2338 >>>>>> sa0: 10.000MB/s transfers (10.000MHz, offset 15) >>>>>> sa0: quirks=3D0x100 >>>>>> sa1 at ahc0 bus 0 scbus0 target 2 lun 0 >>>>>> sa1: Removable Sequential Access = SCSI-2 device=20 >>>>>> sa1: Serial Number CXA09S1340 >>>>>> sa1: 10.000MB/s transfers (10.000MHz, offset 15) >>>>>> sa1: quirks=3D0x100 >>>>>=20 >>>>> If you run 'dmesg', you should have seen a message when it went = away. Perhaps >>>>> there will be something preceding it that will give us a clue = about the >>>>> problem. (Generally a selection timeout.) At least this does = show that >>>>> sa0 is at target 1, and so should not conflict with the library or = sa1. >>>>=20 >>>> Ahh: >>>>=20 >>>> Trying to mount root from zfs:system/bootenv/FreeBSDHEad []... >>>> sa0 at ahc0 bus 0 scbus0 target 1 lun 0 >>>> sa0: s/n CXA22S2338 detached >>>> (sa0:ahc0:0:1:0): Periph destroyed >>>> arp: 10.55.0.60 moved from e4:ce:8f:46:f1:98 to 78:ca:39:fe:d6:b3 = on em0 >>>> arp: 10.55.0.60 moved from e4:ce:8f:46:f1:98 to 78:ca:39:fe:d6:b3 = on em0 >>>> arp: 10.55.0.60 moved from 78:ca:39:fe:d6:b3 to e4:ce:8f:46:f1:98 = on em0 >>>> (sa1:ahc0:0:2:0): 64512-byte tape record bigger than supplied = buffer >>>> (sa1:ahc0:0:2:0): 10240-byte tape record bigger than supplied = buffer Ken, FYI, I upgraded a 9.3 server to 10.2 yesterday. A message similar to the = above is seen here: (sa0:sym0:0:1:0): 64512-byte tape record bigger than supplied buffer Is this just informational? If so, I'll ignore it. >>>=20 >>> Okay. Well, no indication of what happened. Perhaps boot -v will = show it, >>> perhaps not. >>>=20 >>=20 >> Good news. After a reboot, both tape drives are present: >>=20 >> $ ls -l /dev/*sa* >> crw-rw---- 1 root operator 0x61 Mar 2 17:27 /dev/esa0 >> crw-rw---- 1 root operator 0x65 Mar 2 17:27 /dev/esa1 >> crw-rw---- 1 root operator 0x60 Mar 2 17:27 /dev/nsa0 >> crw-rw---- 1 root operator 0x64 Mar 2 17:27 /dev/nsa1 >> crw-rw---- 1 root operator 0x5f Mar 2 17:27 /dev/sa0 >> crw-rw---- 1 root operator 0x5e Mar 2 17:27 /dev/sa0.ctl >> crw-rw---- 1 root operator 0x63 Mar 2 17:27 /dev/sa1 >> crw-rw---- 1 root operator 0x62 Mar 2 17:27 /dev/sa1.ctl >>=20 >=20 > Ahh, good. Glad it is working now! >=20 > Ken > --=20 > Kenneth Merry > ken@FreeBSD.ORG =E2=80=94=20 Dan Langille http://langille.org/ From owner-freebsd-scsi@freebsd.org Mon Aug 24 21:31:17 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 026D19C2389 for ; Mon, 24 Aug 2015 21:31:17 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D604980D for ; Mon, 24 Aug 2015 21:31:16 +0000 (UTC) (envelope-from ken@kdm.org) Received: by mailman.ysv.freebsd.org (Postfix) id D4FF09C2388; Mon, 24 Aug 2015 21:31:16 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D45149C2386; Mon, 24 Aug 2015 21:31:16 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 938FB80B; Mon, 24 Aug 2015 21:31:16 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id t7OLV6SL065653 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 24 Aug 2015 17:31:07 -0400 (EDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id t7OLV6gp065652; Mon, 24 Aug 2015 17:31:06 -0400 (EDT) (envelope-from ken) Date: Mon, 24 Aug 2015 17:31:06 -0400 From: "Kenneth D. Merry" To: Dan Langille Cc: scsi@freebsd.org, current@freebsd.org Subject: Re: sa(4) driver changes available for test Message-ID: <20150824213106.GA65562@mithlond.kdm.org> References: <20150214003232.GA63990@mithlond.kdm.org> <4A478C5C-7965-498E-9F0F-80192265E310@langille.org> <20150302001833.GA71528@mithlond.kdm.org> <6C82281F-649A-4DA8-8ACF-17E81C04F730@langille.org> <20150302003658.GA72258@mithlond.kdm.org> <20150302020608.GA73433@mithlond.kdm.org> <30C55F00-2DE4-4596-96EA-2E3CC40B4DB6@langille.org> <20150302172629.GA87055@mithlond.kdm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Mon, 24 Aug 2015 17:31:07 -0400 (EDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mithlond.kdm.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2015 21:31:17 -0000 On Mon, Aug 24, 2015 at 17:24:22 -0400, Dan Langille wrote: > > > On Mar 2, 2015, at 12:26 PM, Kenneth D. Merry wrote: > > > > On Mon, Mar 02, 2015 at 11:43:15 -0500, Dan Langille wrote: > >> > >>> On Mar 1, 2015, at 9:06 PM, Kenneth D. Merry wrote: > >>> > >>> On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: > >>>> > >>>>> On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry wrote: > >>>>> > >>>>> On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: > >>>>>> > >>>>>>> On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry wrote: > >>>>>>> > >>>>>>> On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: > >>>>>>>> > >>>>>>>>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> I have a fairly large set of changes to the sa(4) driver and mt(1) driver > >>>>>>>>> that I'm planning to commit in the near future. > >>>>>>>>> > >>>>>>>>> A description of the changes is here and below in this message. > >>>>>>>>> > >>>>>>>>> If you have tape hardware and the inclination, I'd appreciate testing and > >>>>>>>>> feedback. > >>>>>>>>> > >>>>>>>>> ============ > >>>>>>>>> Rough draft commit message: > >>>>>>>>> > >>>>>>>>> http://people.freebsd.org/~ken/sa_changes_commitmsg.20150213.3.txt > >>>>>>>>> > >>>>>>>>> The patches against FreeBSD/head as of SVN revision 278706: > >>>>>>>>> > >>>>>>>>> http://people.freebsd.org/~ken/sa_changes.20150213.3.txt > >>>>>>>>> > >>>>>>>>> And (untested) patches against FreeBSD stable/10 as of SVN revision 278721. > >>>>>>>>> > >>>>>>>>> http://people.freebsd.org/~ken/sa_changes.stable_10.20150213.3.txt > >>>>>>>>> ============ > >>>>>>>>> > >>>>>>>>> The intent is to get the tape infrastructure more up to date, so we can > >>>>>>>>> support LTFS and more modern tape drives: > >>>>>>>>> > >>>>>>>>> http://www.ibm.com/systems/storage/tape/ltfs/ > >>>>>>>>> > >>>>>>>>> I have ported IBM's LTFS Single Drive Edition to FreeBSD. The port depends > >>>>>>>>> on the patches linked above. It isn't fully cleaned up and ready for > >>>>>>>>> redistribution. If you're interested, though, let me know and I'll tell > >>>>>>>>> you when it is ready to go out. You need an IBM LTO-5, LTO-6, TS1140 or > >>>>>>>>> TS1150 tape drive. HP drives aren't supported by IBM's LTFS, and older > >>>>>>>>> drives don't have the necessary features to support LTFS. > >>>>>>>>> > >>>>>>>>> The commit message below outlines most of the changes. > >>>>>>>>> > >>>>>>>>> A few comments: > >>>>>>>>> > >>>>>>>>> 1. I'm planning to commit the XPT_DEV_ADVINFO changes separately. > >>>>>>>>> > >>>>>>>>> 2. The XML output is similar to what GEOM and CTL do. It would be nice to > >>>>>>>>> figure out how to put a standard schema on it so that standard tools > >>>>>>>>> could read it. I don't know how feasible that is, since I haven't > >>>>>>>>> time to dig into it. If anyone has suggestions on whether that is > >>>>>>>>> feasible or advisable, I'd appreciate feedback. > >>>>>>>>> > >>>>>>>>> 3. I have tested with a reasonable amount of tape hardware (see below for a > >>>>>>>>> list), but more testing and feedback would be good. > >>>>>>>>> > >>>>>>>>> 4. Standard 'mt status' output looks like this: > >>>>>>>>> > >>>>>>>>> # mt -f /dev/nsa3 status -v > >>>>>>>>> Drive: sa3: Serial Number: 101500520A > >>>>>>>>> --------------------------------- > >>>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>>> Current: 0x5a:LTO-6 variable 384607 enabled (0xff) > >>>>>>>>> --------------------------------- > >>>>>>>>> Current Driver State: at rest. > >>>>>>>>> --------------------------------- > >>>>>>>>> Partition: 0 Calc File Number: 0 Calc Record Number: 0 > >>>>>>>>> Residual: 0 Reported File Number: 0 Reported Record Number: 0 > >>>>>>>>> Flags: BOP > >>>>>>>>> > >>>>>>>>> 5. 'mt status -v' looks like this: > >>>>>>>>> > >>>>>>>>> # mt -f /dev/nsa3 status -v > >>>>>>>>> Drive: sa3: Serial Number: 101500520A > >>>>>>>>> --------------------------------- > >>>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>>> Current: 0x5a:LTO-6 variable 384607 enabled (0xff) > >>>>>>>>> --------------------------------- > >>>>>>>>> Current Driver State: at rest. > >>>>>>>>> --------------------------------- > >>>>>>>>> Partition: 0 Calc File Number: 0 Calc Record Number: 0 > >>>>>>>>> Residual: 0 Reported File Number: 0 Reported Record Number: 0 > >>>>>>>>> Flags: BOP > >>>>>>>>> --------------------------------- > >>>>>>>>> Tape I/O parameters: > >>>>>>>>> Maximum I/O size allowed by driver and controller (maxio): 1081344 bytes > >>>>>>>>> Maximum I/O size reported by controller (cpi_maxio): 5197824 bytes > >>>>>>>>> Maximum block size supported by tape drive and media (max_blk): 8388608 bytes > >>>>>>>>> Minimum block size supported by tape drive and media (min_blk): 1 bytes > >>>>>>>>> Block granularity supported by tape drive and media (blk_gran): 0 bytes > >>>>>>>>> Maximum possible I/O size (max_effective_iosize): 1081344 bytes > >>>>>>>> > >>>>>>>> > >>>>>>>> # mtx -f /dev/pass0 status > >>>>>>>> Storage Changer /dev/pass0:2 Drives, 10 Slots ( 0 Import/Export ) > >>>>>>>> Data Transfer Element 0:Empty > >>>>>>>> Data Transfer Element 1:Empty > >>>>>>>> Storage Element 1:Empty > >>>>>>>> Storage Element 2:Empty > >>>>>>>> Storage Element 3:Empty > >>>>>>>> Storage Element 4:Full :VolumeTag=FAI260 > >>>>>>>> Storage Element 5:Full :VolumeTag=FAI261 > >>>>>>>> Storage Element 6:Full :VolumeTag=FAI262 > >>>>>>>> Storage Element 7:Full :VolumeTag=FAI263 > >>>>>>>> Storage Element 8:Empty > >>>>>>>> Storage Element 9:Empty > >>>>>>>> Storage Element 10:Empty > >>>>>>>> > >>>>>>>> > >>>>>>>> It was at this point I spent the next 90 minute trying to get the tape > >>>>>>>> drive out of the tape library to free a stuck tape. Some of this was spent > >>>>>>>> attempting, and failing, to undo a stripped screw. I stopped the attempt when > >>>>>>>> I noticed the screw did need to be removed. :/ > >>>>>>> > >>>>>>> Thanks for all of the effort! Looks like it is paying off! :) > >>>>>>> > >>>>>>>> When I do this command, I hear the drive move a bit, to read the tape: > >>>>>>>> > >>>>>>>> # mt -f /dev/nsa1 status > >>>>>>>> Drive: sa1: Serial Number: CXA09S1340 > >>>>>>>> --------------------------------- > >>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 enabled (IDRC) > >>>>>>>> --------------------------------- > >>>>>>>> Current Driver State: at rest. > >>>>>>>> --------------------------------- > >>>>>>>> Partition: 0 Calc File Number: 0 Calc Record Number: 0 > >>>>>>>> Residual: 0 Reported File Number: -1 Reported Record Number: -1 > >>>>>>>> Flags: None > >>>>>>> > >>>>>>> Looks like the drive isn't reporting position information. It will still > >>>>>>> be useful to try it with Bacula, though. > >>>>>>> > >>>>>>>> # mt -f /dev/nsa1 ostatus > >>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> ---------available modes--------- > >>>>>>>> 0: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 1: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 2: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 3: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> --------------------------------- > >>>>>>>> Current Driver State: at rest. > >>>>>>>> --------------------------------- > >>>>>>>> File Number: 0 Record Number: 0 Residual Count 0 > >>>>>>>> > >>>>>>>> > >>>>>>>> After doing a very small tar -c and tar -x, I have: > >>>>>>>> > >>>>>>>> # mt -f /dev/nsa1 /dev/nsa1 ostatus > >>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> ---------available modes--------- > >>>>>>>> 0: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 1: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 2: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> 3: 0x1b:DLTapeIV(35GB) variable 85937 IDRC > >>>>>>>> --------------------------------- > >>>>>>>> Current Driver State: at rest. > >>>>>>>> --------------------------------- > >>>>>>>> File Number: 0 Record Number: 7 Residual Count 0 > >>>>>>> > >>>>>>> Woohoo! It works. > >>>>>>> > >>>>>>>> # mt -f /dev/nsa1 status -v > >>>>>>>> Drive: sa1: Serial Number: CXA09S1340 > >>>>>>>> --------------------------------- > >>>>>>>> Mode Density Blocksize bpi Compression > >>>>>>>> Current: 0x1b:DLTapeIV(35GB) variable 85937 enabled (IDRC) > >>>>>>>> --------------------------------- > >>>>>>>> Current Driver State: at rest. > >>>>>>>> --------------------------------- > >>>>>>>> Partition: 0 Calc File Number: 0 Calc Record Number: 7 > >>>>>>>> Residual: 0 Reported File Number: -1 Reported Record Number: -1 > >>>>>>>> Flags: None > >>>>>>>> --------------------------------- > >>>>>>>> Tape I/O parameters: > >>>>>>>> Maximum I/O size allowed by driver and controller (maxio): 65536 bytes > >>>>>>>> Maximum I/O size reported by controller (cpi_maxio): 0 bytes > >>>>>>>> Maximum block size supported by tape drive and media (max_blk): 16777214 bytes > >>>>>>>> Minimum block size supported by tape drive and media (min_blk): 2 bytes > >>>>>>>> Block granularity supported by tape drive and media (blk_gran): 0 bytes > >>>>>>>> Maximum possible I/O size (max_effective_iosize): 65536 bytes > >>>>>>>> > >>>>>>>> I may not get to testing Bacula today. > >>>>>>>> > >>>>>>>> Based on the above, is there any commands you'd like me to try? > >>>>>>> > >>>>>>> Aside from making sure things work okay with Bacula, that is probably > >>>>>>> sufficient. These drives won't support density reports or position > >>>>>>> information. > >>>>>>> > >>>>>>>> Read below regarding two tape drives > >>>>>>>> > >>>>>>>>> > >>>>>>>>> 6. Existing applications should work without changes. If not, please let > >>>>>>>>> me know. Hopefully they will move over time to the new interfaces. > >>>>>>>>> > >>>>>>>>> 7. There are lots of additional features that could be added later. > >>>>>>>>> Append-only support, encryption, more log pages, etc. > >>>>>>>>> > >>>>>>>>> 8. I have SCSI READ ATTRIBUTE changes for camcontrol(8) that will go in > >>>>>>>>> separately. These changes allow displaying the contents of the MAM > >>>>>>>>> (Medium Auxiliary Memory) chips on LTO, TS and other modern tape drives. > >>>>>>>>> These are good, and a future possible direction is adding attributes > >>>>>>>>> to the status XML from the sa(4) driver. > >>>>>>>>> > >>>>>>>>> ============ > >>>>>>>>> Significant upgrades to sa(4) and mt(1). > >>>>>>>>> > >>>>>>>>> The primary focus of these changes is to modernize FreeBSD's > >>>>>>>>> tape infrastructure so that we can take advantage of some of the > >>>>>>>>> features of modern tape drives and allow support for LTFS. > >>>>>>>>> > >>>>>>>>> Significant changes and new features include: > >>>>>>>>> > >>>>>>>>> o sa(4) driver status and parameter information is now exported via an > >>>>>>>>> XML structure. This will allow for changes and improvements later > >>>>>>>>> on that will not break userland applications. The old MTIOCGET > >>>>>>>>> status ioctl remains, so applications using the existing interface > >>>>>>>>> will not break. > >>>>>>>>> > >>>>>>>>> o 'mt status' now reports drive-reported tape position information > >>>>>>>>> as well as the previously available calculated tape position > >>>>>>>>> information. These numbers will be different at times, because > >>>>>>>>> the drive-reported block numbers are relative to BOP (Beginning > >>>>>>>>> of Partition), but the block numbers calculated previously via > >>>>>>>>> sa(4) (and still provided) are relative to the last filemark. > >>>>>>>>> Both numbers are now provided. 'mt status' now also shows the > >>>>>>>>> drive INQUIRY information, serial number and any position flags > >>>>>>>>> (BOP, EOT, etc.) provided with the tape position information. > >>>>>>>>> 'mt status -v' adds information on the maximum possible I/O size, > >>>>>>>>> and the underlying values used to calculate it. > >>>>>>>>> > >>>>>>>>> o The extra sa(4) /dev entries (/dev/saN.[0-3]) have been removed. > >>>>>>>> > >>>>>>>> How does this affect a tape library with more than one tape drive? > >>>>>>>> > >>>>>>>> [root@cuppy:~] # camcontrol amcontrol devlist > >>>>>>>> at scbus0 target 0 lun 0 (pass0,ch0) > >>>>>>>> at scbus0 target 2 lun 0 (sa1,pass2) > >>>>>>>> at scbus1 target 0 lun 0 (pass3,ada0) > >>>>>>>> at scbus2 target 0 lun 0 (pass4,ada1) > >>>>>>>> at scbus3 target 0 lun 0 (pass5,ses0) > >>>>>>>> > >>>>>>>> This system has two tapes drives and I can access them through the front panel but: > >>>>>>>> > >>>>>>>> # ls -l /dev/*sa* > >>>>>>>> crw-rw---- 1 root operator 0x65 Feb 28 22:04 /dev/esa1 > >>>>>>>> crw-rw---- 1 root operator 0x64 Mar 1 22:43 /dev/nsa1 > >>>>>>>> crw-rw---- 1 root operator 0x63 Feb 28 22:04 /dev/sa1 > >>>>>>>> crw-rw---- 1 root operator 0x62 Feb 28 22:04 /dev/sa1.ctl > >>>>>>>> > >>>>>>>> ... only one tape drives shows up. > >>>>>>> > >>>>>>> > >>>>>>> Hmm. The tape drive is listed as sa1, which implies that there may be an > >>>>>>> sa0 that was there previously or is in the process of probing. What does > >>>>>>> dmesg show? How about 'camcontrol devlist -v'? > >>>>>> > >>>>>> # camcontrol devlist -v > >>>>>> scbus0 on ahc0 bus 0: > >>>>>> at scbus0 target 0 lun 0 (pass0,ch0) > >>>>>> at scbus0 target 2 lun 0 (sa1,pass2) > >>>>>> <> at scbus0 target -1 lun ffffffff () > >>>>>> scbus1 on ahcich2 bus 0: > >>>>>> at scbus1 target 0 lun 0 (pass3,ada0) > >>>>>> <> at scbus1 target -1 lun ffffffff () > >>>>>> scbus2 on ahcich4 bus 0: > >>>>>> at scbus2 target 0 lun 0 (pass4,ada1) > >>>>>> <> at scbus2 target -1 lun ffffffff () > >>>>>> scbus3 on ahciem0 bus 0: > >>>>>> at scbus3 target 0 lun 0 (pass5,ses0) > >>>>>> <> at scbus3 target -1 lun ffffffff () > >>>>>> scbus-1 on xpt0 bus 0: > >>>>>> <> at scbus-1 target -1 lun ffffffff (xpt0) > >>>>>> > >>>>>> > >>>>>> BUT! > >>>>>> > >>>>>> # grep sa /var/run/dmesg.boot > >>>>>> VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID > >>>>>> module_register_init: MOD_LOAD (vesa, 0xffffffff80de3720, 0) error 19 > >>>>>> alc0: Using 1 MSIX message(s). > >>>>>> isab0: at device 31.0 on pci0 > >>>>>> isa0: on isab0 > >>>>>> orm0: at iomem 0xce800-0xcefff on isa0 > >>>>>> atkbdc0: at port 0x60,0x64 on isa0 > >>>>>> sa0 at ahc0 bus 0 scbus0 target 1 lun 0 > >>>>>> sa0: Removable Sequential Access SCSI-2 device > >>>>>> sa0: Serial Number CXA22S2338 > >>>>>> sa0: 10.000MB/s transfers (10.000MHz, offset 15) > >>>>>> sa0: quirks=0x100 > >>>>>> sa1 at ahc0 bus 0 scbus0 target 2 lun 0 > >>>>>> sa1: Removable Sequential Access SCSI-2 device > >>>>>> sa1: Serial Number CXA09S1340 > >>>>>> sa1: 10.000MB/s transfers (10.000MHz, offset 15) > >>>>>> sa1: quirks=0x100 > >>>>> > >>>>> If you run 'dmesg', you should have seen a message when it went away. Perhaps > >>>>> there will be something preceding it that will give us a clue about the > >>>>> problem. (Generally a selection timeout.) At least this does show that > >>>>> sa0 is at target 1, and so should not conflict with the library or sa1. > >>>> > >>>> Ahh: > >>>> > >>>> Trying to mount root from zfs:system/bootenv/FreeBSDHEad []... > >>>> sa0 at ahc0 bus 0 scbus0 target 1 lun 0 > >>>> sa0: s/n CXA22S2338 detached > >>>> (sa0:ahc0:0:1:0): Periph destroyed > >>>> arp: 10.55.0.60 moved from e4:ce:8f:46:f1:98 to 78:ca:39:fe:d6:b3 on em0 > >>>> arp: 10.55.0.60 moved from e4:ce:8f:46:f1:98 to 78:ca:39:fe:d6:b3 on em0 > >>>> arp: 10.55.0.60 moved from 78:ca:39:fe:d6:b3 to e4:ce:8f:46:f1:98 on em0 > >>>> (sa1:ahc0:0:2:0): 64512-byte tape record bigger than supplied buffer > >>>> (sa1:ahc0:0:2:0): 10240-byte tape record bigger than supplied buffer > > Ken, > > FYI, I upgraded a 9.3 server to 10.2 yesterday. A message similar to the above is seen here: > > (sa0:sym0:0:1:0): 64512-byte tape record bigger than supplied buffer > > Is this just informational? If so, I'll ignore it. Yes, it's informational. It tells you that your tape blocks are 64512 bytes long. Or at least the first one is. The initial tape mount inside the sa(4) driver does a test read with an 8K buffer. This is to get the drive to actually look at the media, so it will know what is there. (This is necessary on some older drives.) We don't necessarily expect that the initial read will read in a whole block, but the sense data that comes back from the tape drive will tell you how big the first block is at least. We could silence it, or perhaps use a bigger (e.g. MAXPHYS) buffer, so you'd get an error in the case where we can't read the blocksize written to the tape. I think it is somewhat helpful to know how big the blocksize is. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@freebsd.org Thu Aug 27 00:01:43 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF8529C3480 for ; Thu, 27 Aug 2015 00:01:43 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9484B9F0 for ; Thu, 27 Aug 2015 00:01:42 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from peevish.spa.umn.edu ([128.101.220.230]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZUkdR-0005bZ-Tg for freebsd-scsi@freebsd.org; Wed, 26 Aug 2015 19:01:41 -0500 To: freebsd-scsi@freebsd.org From: Graham Allan Subject: Re: mps driver on 10.2-BETA Organization: Physics, University of Minnesota Message-ID: <55DE5365.6090608@physics.umn.edu> Date: Wed, 26 Aug 2015 19:01:41 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 00:01:43 -0000 Now that 10.2-RELEASE is out, I'm looking at it more closely as well. There was another bug report at FreeNAS related to this which appeared to lead to more concrete evidence of firmware 20.00.00.00 being "bad": https://bugs.freenas.org/issues/7384 the nexenta reference (which seems to include LSI acknowledging a fault) can be found here: https://community.nexenta.com/thread/1053 I was running FreeBSD 9.3 and certainly saw bad behaviour with firmware 20.00.00.00, while 19.00.00.00 and 16.00.00.00 both seemed ok. Anyway it would be nice if there could be some kind of reassurance that 20.00.00.04 is indeed fixed and safe to use, as it seems we are intended to use firmware matching the v20 driver in 10.2. I couldn't find any firmware release notes. Graham -- From owner-freebsd-scsi@freebsd.org Thu Aug 27 00:09:36 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9135A9C35D8 for ; Thu, 27 Aug 2015 00:09:36 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 62F52B61 for ; Thu, 27 Aug 2015 00:09:35 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from peevish.spa.umn.edu ([128.101.220.230]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZUkPd-0005CQ-1U for freebsd-scsi@freebsd.org; Wed, 26 Aug 2015 18:47:25 -0500 To: freebsd-scsi@freebsd.org From: Graham Allan Subject: kernel panic on 9.3 with mps reinit Organization: Physics, University of Minnesota Message-ID: <55DE5008.7000504@physics.umn.edu> Date: Wed, 26 Aug 2015 18:47:20 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 00:09:36 -0000 I have a biggish zfs file server running 9.3-RELEASE-p19 which has a habit of panicking during drive add/remove/scan operations. We made the mistake of using some "not great" desktop drives for our first pool, so there is some turnover of drives through failure. What I find is we can generally replace 2-3 drives over a period of some months, then at some point new drives are no longer recognised, either upon insertion or with "camcontrol rescan". Under 9.1, I found that running "sas2ircu 0 DISPLAY" would (after waiting for a timeout) reinitialize the mps controller, the drives would be found, and we could continue. But on 9.3, the same attempt results in a panic. Attached I have some remotely-received syslog output from a spontaneous panic when a drive suffered hardware failure - looks like the same pattern, with panic shortly after mps reinit. This might be somewhat useless as I have never got a crash dump out of this system; possibly swap is too much smaller than RAM to get a minidump. But if you have any suggestions to debug further I'd welcome them. The system has four Supermicro SC847-JBOD drive chassis attached to a single 9207-8e controller (this used to be one controller per chassis but we had other issues with that back on FreeBSD 9.1). It can operate under heavy load for months on end so I don't believe cabling problems are an issue, it seems mostly related to state after drive loss. Thanks in advance for any suggestions, Graham > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): READ(10). CDB: 28 00 26 0b df 90 00 00 e8 00 length 118784 SMID 772 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): READ(6). CDB: 08 00 02 10 10 00 length 8192 SMID 477 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): READ(16). CDB: 88 00 00 00 00 01 5d 50 9e 10 00 00 00 10 00 00 length 8192 SMID 212 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): READ(16). CDB: 88 00 00 00 00 01 5d 50 a0 10 00 00 00 10 00 00 length 8192 SMID 174 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): READ(10). CDB: 28 00 26 0b de a8 00 00 e8 00 > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information) > Aug 22 15:16:46 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): READ(10). CDB: 28 00 26 0b de a8 00 00 e8 00 length 118784 SMID 921 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): READ(10). CDB: 28 00 26 0b df 90 00 00 e8 00 length 118784 SMID 877 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): READ(6). CDB: 08 00 02 10 10 00 length 8192 SMID 330 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): READ(16). CDB: 88 00 00 00 00 01 5d 50 a0 10 00 00 00 10 00 00 length 8192 SMID 461 terminated ioc 804b scsi 0 state 0 xfer 0 > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): READ(16). CDB: 88 00 00 00 00 01 5d 50 9e 10 00 00 00 10 00 00 > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information) > Aug 22 15:16:55 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information) > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): Error 5, Retries exhausted > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): READ(10). CDB: 28 00 32 5a d1 c0 00 00 20 00 > Aug 22 18:56:19 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > ... snip ... > Aug 22 18:56:25 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:25 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:25 hostname kernel: (da58:mps0:0:87:0): Error 5, Retries exhausted > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Error 5, Retries exhausted > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Error 5, Retries exhausted > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Retrying command (per sense data) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): CAM status: SCSI Status Error > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI status: Check Condition > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure) > Aug 22 18:56:26 hostname kernel: (da58:mps0:0:87:0): Error 5, Retries exhausted > Aug 22 18:56:49 hostname kernel: da58 at mps0 bus 0 scbus0 target 87 lun 0 > Aug 22 18:56:49 hostname kernel: da58: s/n WD-WCC1T0276990 detached > Aug 22 18:56:49 hostname kernel: (da58:mps0:0:87:0): Periph destroyed > Aug 22 18:56:52 hostname kernel: mpssas_get_sata_identify: error reading SATA PASSTHRU; iocstatus = 0x804b > Aug 22 18:56:53 hostname kernel: mps0: _mapping_add_new_device: failed to add the device with handle 0x00a8 to persistent table because there is no free space available > Aug 22 18:57:53 hostname kernel: mps0: Calling Reinit from mps_wait_command > Aug 22 18:57:53 hostname kernel: mps0: Reinitializing controller, > Aug 22 18:57:54 hostname kernel: mps0: Firmware: 16.00.00.00, Driver: 16.00.00.00-fbsd > Aug 22 18:57:54 hostname kernel: mps0: IOCCapabilities: 1a85c > Aug 22 18:57:54 hostname kernel: mps0: mps_reinit finished sc 0xffffff8001877000 post 4 free 3 > Aug 22 18:57:54 hostname kernel: mps0: Reinit success > Aug 22 18:57:54 hostname kernel: mpssas_get_sata_identify: request for page completed with error 60failure at /usr/src/sys/dev/mps/mps_sas_lsi.c:667/mpssas_add_device()! Could not get ID for device with handle 0x00a8 > Aug 22 18:57:54 hostname kernel: mpssas_fw_work: failed to add device with handle 0xa8 > Aug 22 18:57:54 hostname kernel: _mapping_update_missing_count: device is already removed from mapping table > Aug 22 18:57:56 hostname kernel: > Aug 22 18:57:56 hostname kernel: > Aug 22 18:57:56 hostname kernel: Fatal trap 12: page fault while in kernel mode > Aug 22 18:57:56 hostname kernel: cpuid = 2; apic id = 02 > Aug 22 18:57:56 hostname kernel: fault virtual address#011= 0x0 > Aug 22 18:57:56 hostname kernel: fault code#011#011= supervisor write data, page not present > Aug 22 18:57:56 hostname kernel: instruction pointer#011= 0x20:0xffffffff805bbc19 > Aug 22 18:57:56 hostname kernel: stack pointer#011 = 0x28:0xffffff905c4dc640 > Aug 22 18:57:56 hostname kernel: frame pointer#011 = 0x28:0xffffff905c4dc650 > Aug 22 18:57:56 hostname kernel: code segment#011#011= base 0x0, limit 0xfffff, type 0x1b > Aug 22 18:57:56 hostname kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > Aug 22 18:57:56 hostname kernel: processor eflags#011= interrupt enabled, resume, IOPL = 0 > Aug 22 18:57:56 hostname kernel: current process#011#011= 0 (mps0 taskq) > Aug 22 18:57:56 hostname kernel: trap number#011#011= 12 -- From owner-freebsd-scsi@freebsd.org Thu Aug 27 06:20:18 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 643329C2C8E for ; Thu, 27 Aug 2015 06:20:18 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 251A114E; Thu, 27 Aug 2015 06:20:17 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPSA id 892929DDD11; Thu, 27 Aug 2015 08:10:24 +0200 (CEST) Subject: Re: mps driver on 10.2-BETA Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <882392fa1d2e36a4c2de036790b9f215@mail.gmail.com> Date: Thu, 27 Aug 2015 08:10:18 +0200 Cc: Dan Langille , slm@freebsd.org, freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <67F2E033-787D-49DF-9328-2608A5EEB83A@sarenet.es> References: <8F3CEA48-F00B-4CA7-AB23-0CE8783E1969@langille.org> <882392fa1d2e36a4c2de036790b9f215@mail.gmail.com> To: Stephen Mcconnell X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 06:20:18 -0000 On Jul 23, 2015, at 10:53 PM, Stephen Mcconnell wrote: > Hi Dan, >=20 > I don't know about this problem with P20. I would recommend that you = use > the latest FW available, and it looks like you've done that. Let me = know if > you have any problems with it. Sorry that I can't be more help than = that. At least I have one example in which using the latest version was a = problem. http://lists.freebsd.org/pipermail/freebsd-scsi/2014-October/006505.html It affected P19 though, I haven't tried P20 yet. Cheers, Borja. From owner-freebsd-scsi@freebsd.org Thu Aug 27 09:30:33 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B11EE9C48A9 for ; Thu, 27 Aug 2015 09:30:33 +0000 (UTC) (envelope-from k.kulikov2@gmail.com) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DAA91EB5 for ; Thu, 27 Aug 2015 09:30:33 +0000 (UTC) (envelope-from k.kulikov2@gmail.com) Received: by labns7 with SMTP id ns7so8542743lab.0 for ; Thu, 27 Aug 2015 02:30:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=dAXnsOv7tMyN2d1WfEwn7jmFwakmLAwOEL5VA8BFSeY=; b=0wegfFOj1Z1M7gY9D3zu5iL/t9unQ5hvAE4xT7sD4jH/UnX6RerztJ4EGWf7GfRA3u 29YQalLFNPqLV7MPZpvHf0tZxY+fEIQVCYBYJF2QbOECuA1jg4uwb3/SiUmNGxezPj7Z +N/SSNwGKBozJZ0h+zHEp9ZFn0uxzcq4qx6OlCnKL0bFHBJcdaUjorDTClZx0hVJ9v8z 75yxGvh2pEwUDOg8wGmvNc4XNIIgcFDW4xIGujkPbX3zBTalPwkQE5NnagSm8VezFJDH uXMD4769QpD/8SLfUNguekx+gnWtURlDJgkLM15RRUelfWVSTROfiedwX6amYC/CXPwT Pwaw== X-Received: by 10.112.125.34 with SMTP id mn2mr1460650lbb.76.1440667831118; Thu, 27 Aug 2015 02:30:31 -0700 (PDT) MIME-Version: 1.0 References: <55DE5365.6090608@physics.umn.edu> In-Reply-To: <55DE5365.6090608@physics.umn.edu> From: Konstantin Kulikov Date: Thu, 27 Aug 2015 09:30:21 +0000 Message-ID: Subject: Re: mps driver on 10.2-BETA To: Graham Allan , freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 09:30:33 -0000 Hey. I will get a new LSI card in maybe two weeks and will test with new firmware and 10.2-RELEASE. On Thu, Aug 27, 2015 at 3:01 AM Graham Allan wrote: > Now that 10.2-RELEASE is out, I'm looking at it more closely as well. > > There was another bug report at FreeNAS related to this which appeared > to lead to more concrete evidence of firmware 20.00.00.00 being "bad": > > https://bugs.freenas.org/issues/7384 > > the nexenta reference (which seems to include LSI acknowledging a fault) > can be found here: > https://community.nexenta.com/thread/1053 > > I was running FreeBSD 9.3 and certainly saw bad behaviour with firmware > 20.00.00.00, while 19.00.00.00 and 16.00.00.00 both seemed ok. > > Anyway it would be nice if there could be some kind of reassurance that > 20.00.00.04 is indeed fixed and safe to use, as it seems we are intended > to use firmware matching the v20 driver in 10.2. I couldn't find any > firmware release notes. > > Graham > -- > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@freebsd.org Thu Aug 27 14:33:03 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85AD69C38F5 for ; Thu, 27 Aug 2015 14:33:03 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68BCFE5E for ; Thu, 27 Aug 2015 14:33:01 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from c-66-41-25-68.hsd1.mn.comcast.net ([66.41.25.68] helo=[192.168.0.117]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZUyEd-0007DO-MZ; Thu, 27 Aug 2015 09:32:59 -0500 Subject: Re: mps driver on 10.2-BETA To: Konstantin Kulikov , freebsd-scsi@freebsd.org References: <55DE5365.6090608@physics.umn.edu> From: Graham Allan Message-ID: <55DF1F78.2080204@physics.umn.edu> Date: Thu, 27 Aug 2015 09:32:24 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 14:33:03 -0000 I definitely had the same issues others reported with the 20.00.00.00 firmware (though using FreeBSD 9.3). I was building a new system at the time so was able to stress test it with different firmware versions - 20 gave errors, 19 and 16 were fine. I have another system which isn't in production yet - I can do the same test on that and see if the newer 20.00.00.04 is stable. This is also running 9.3 but the test should still be valid. I will be using this system for 10.2 testing, but would like to keep it on 9.3 for a short time to try and resolve any issues with that. I wonder if some advice about firmware could be added to the mps man page? Even at this point I'm not certain what the absolute best practice is, whether driver and firmware versions should match, or (as FreeNAS developers seemed to imply) firmware should be >= driver. Graham On 8/27/2015 4:30 AM, Konstantin Kulikov wrote: > Hey. > I will get a new LSI card in maybe two weeks and will test with new > firmware and 10.2-RELEASE. > From owner-freebsd-scsi@freebsd.org Thu Aug 27 20:12:19 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2368C9C315B for ; Thu, 27 Aug 2015 20:12:19 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01A7EAAB for ; Thu, 27 Aug 2015 20:12:17 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from spa-sysadm-01.spa.umn.edu ([134.84.199.8]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZV3Wx-000LDi-Vc for freebsd-scsi@freebsd.org; Thu, 27 Aug 2015 15:12:15 -0500 Message-ID: <55DF6F1F.9070909@physics.umn.edu> Date: Thu, 27 Aug 2015 15:12:15 -0500 From: Graham Allan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: mps driver on 10.2-BETA References: <55DE5365.6090608@physics.umn.edu> <55DF1F78.2080204@physics.umn.edu> In-Reply-To: <55DF1F78.2080204@physics.umn.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 20:12:19 -0000 On 8/27/2015 9:32 AM, Graham Allan wrote: > > I have another system which isn't in production yet - I can do the same > test on that and see if the newer 20.00.00.04 is stable. This is also > running 9.3 but the test should still be valid. I will be using this > system for 10.2 testing, but would like to keep it on 9.3 for a short > time to try and resolve any issues with that. I updated the firmware on this HBA to 20.00.04.00 and ran some stress tests - all looks fine after 4+ hours. I'm pretty certain that issues showed up long before that with 20.00.00.00 (ideally I'd like to retest that, but I don't have a stashed copy of that firmware). To reiterate, this is with FreeBSD 9.3, and in this particular case the HBA is a 9205-8e. I expect I'll get to re-test within the next few weeks with FreeBSD 10.2. But for now it seems like firmware 20.00.04.00 has the previous problems fixed. Graham