Date: Tue, 13 Oct 2015 16:42:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191348] [mps] LSI2308 with WD3000FYYZ drives disappears after hotswapping Message-ID: <bug-191348-8-BQgQ9AKbbe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-191348-8@https.bugs.freebsd.org/bugzilla/> References: <bug-191348-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191348 --- Comment #31 from Karli.Sjoberg@slu.se --- (In reply to Stephen McConnell from comment #30) OK, yeah we=C2=B4re on the same page. The drive doesn=C2=B4t show up but th= erein ends the similarities. OK, driver timeout is more appropriate but lies at the OS level, as opposed= to setting in HBA or HDD firmware, is what I meant. There are no simple reproduction steps I can provide because I can=C2=B4t r= eally make it happen at will, but it has happened quite frequently as of late. Wh= at I can tell you are how the systems are setup. You start with some hardware, add a HBA of either model 9200, 9201, 9211 or AOC-USAS2-L8(i|e) flashed with IT FW, connect them through some kind of expander and add at least 14 drives. That=C2=B4s the least amount of drives= where I=C2=B4ve seen this issue occur. Install latest FreeBSD release and opt for= "Auto ZFS", apply some pressure (preferably external over NFS, iSCSI, SMB or something) for a few days and then watch the magic happen. Lots of concurrent IO seems to trigger it more frequently. /K --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191348-8-BQgQ9AKbbe>