Hey all,
Recently hooked up a ton of DS2246 w 900g drives to some 6080s and 6280s running (ancient) cDOT 8.0.5, and am seeing a lot of sas.adapter.debug messages when the aggregates in question are under heavy write load.
Seeing this on multiple filers, multiple adapters, so I'm guessing it's a bug of some sort, which was likely fixed years ago?
These don't appear to be impacting performance as far as I can tell, but I'm not certain (gear was just onlined, and using this as staging area for shuffling lots of volumes around).
Are these particularly evil? Can't find much online about them, but they don't look very appealing:
Oct 24 18:17:47 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="OPEN timeout (0x13): dev 5b.13.13 (5:000039:7385204:66), cdb 0x2a:236f16d8:0200 (0/29311), NDU 0x0" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x2a:236f16d8:0200" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x2a:236f18d8:0200" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x28:236f3620:0010" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x28:1555e6f8:0080" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x2a:236f1ad8:0200" Oct 24 18:17:51 filer1a pmcsas_intrd_1: sas.adapter.debug: adapterName="5a", debug_string="Bad device state completion: status 0x39, dev 5b.13.13, cdb 0x2f:041a4800:0400" Oct 24 19:21:46 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.15.22 (5:000039:73850ad:19), cdb 0x2a:2368ed60:0200 (0/18656), NDU 0x0" Oct 24 19:21:49 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.22, cdb 0x2a:2368ed60:0200" Oct 24 19:21:49 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.22, cdb 0x2f:04dd0800:0400" Oct 24 19:24:01 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.15.0 (5:000039:7481142:e5), cdb 0x2a:2382c048:0200 (0/33634), NDU 0x0" Oct 24 19:24:01 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.0, cdb 0x2a:2382bc48:0200" Oct 24 19:24:01 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.0, cdb 0x2a:2382c248:0200" Oct 24 19:30:02 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.16.19 (5:000039:7480858:65), cdb 0x2a:23ca4d38:0200 (0/74568), NDU 0x0" Oct 24 19:30:02 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.16.19, cdb 0x2a:23ca4f38:0200" Oct 24 19:31:21 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.15.0 (5:000039:7481142:e5), cdb 0x2a:23f9dd80:0200 (0/439), NDU 0x0" Oct 24 19:31:21 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.0, cdb 0x2a:23f9df80:0200" Oct 24 19:31:34 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.15.2 (5:000039:7480859:bd), cdb 0x28:0871dd38:0008 (0/74660), NDU 0x0" Oct 24 19:31:34 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.15.2, cdb 0x2a:23fca318:00e8" Oct 24 19:33:40 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="OPEN timeout (0x13): dev 1a.16.6 (5:000039:7481143:01), cdb 0x2a:24176530:0198 (0/74786), NDU 0x0" Oct 24 19:33:40 filer1a pmcsas_intrd_2: sas.adapter.debug: adapterName="1a", debug_string="Bad device state completion: status 0x39, dev 1a.16.6, cdb 0x2a:241766c8:0200"
Where to begin?
If your ONTAP is that old...what about disk shelf firmware? disk firmware? Even the SAS adapter has a firmware update when ONTAP gets updated.
Tried a quick seach and could not find anything, but might be worth checking the disk/shelf firmware and getting them up to date.
Schedule a time to update ontap to 8.2.4P5 to get current?
On Mon, Oct 24, 2016 at 10:38 PM, Mike Thompson mike.thompson@gmail.com wrote:
pmcsas_intrd_1: sas.adapter.debug
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
*I Blog at TMACsRack https://tmacsrack.wordpress.com/*
[image: NetApp - In partnership with Alpine Testing Solutions][image: NetApp Certified Data Administrator, ONTAP] https://www.certmetrics.com/netapp/public/badge.aspx?t=c&d=2012-11-05&i=35&ci=NETAPP00041276[image: NetApp Certified Implementation Engineer - SAN Specialist, ONTAP] https://www.certmetrics.com/netapp/public/badge.aspx?t=c&d=2012-11-08&i=36&ci=NETAPP00041276[image: NetApp Certified Storage Installation Engineer, ONTAP] https://www.certmetrics.com/netapp/public/badge.aspx?t=c&d=2015-10-13&i=38&ci=NETAPP00041276[image: NetApp Certified Implementation Engineer - Data Protection Specialist] https://www.certmetrics.com/netapp/public/badge.aspx?t=c&d=2015-10-15&i=11&ci=NETAPP00041276
NetApp Candidate ID: NETAPP00041276 FlexPod Design: Oct 2015 - Jan 2018, S0N62WE1BMVEYF3M FlexPod Implementation: Oct 2015 - Jan 2018, JH3QJT4KLEQ41HPH
RHCE6 110-107-141 https://www.redhat.com/wapps/training/certification/verify.html?certNumber=110-107-141&isSearch=False&verify=Verify
gear isn't on support, so i'm not updating Ontap.
all the SAS shelves brand new though, so should have latest firmware, but i'll double check.