<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Same issue here around two months ago when a L2arc device failed… failmode was default and the device was actually an mSata SSD mounted in a PCI-E mSata card:<o:p></o:p> <o:p> </o:p> <a href="http://www.addonics.com/products/ad4mspx2.php">http://www.addonics.com/products/ad4mspx2.php</a> and the disk was one of four of these <a href="http://www.samsung.com/us/computer/memory-storage/MZ-MTE1T0BW">http://www.samsung.com/us/computer/memory-storage/MZ-MTE1T0BW</a><o:p></o:p> <o:p> </o:p> Can these reboots be avoided in any way?<o:p></o:p> <o:p> </o:p> Br,<o:p></o:p> Rune<o:p></o:p> <o:p></o:p> From: OmniOS-discuss [mailto:omnios-discuss-bounces@lists.omniti.com] On Behalf Of Schweiss, Chip Sent: Monday, May 18, 2015 10:31 PM To: Paul B. Henson Cc: omnios-discuss Subject: Re: [OmniOS-discuss] disk failure causing reboot?<o:p></o:p> <o:p> </o:p> <div> <div> <div> <div> I had the exact same failure mode last week. With over 1000 spindles I see this about once a month. I can publish my dump also if anyone actually want's to try to fix this problem, but I think there are several of the same thing already linked to tickets in Illumos-gate.<o:p></o:p> </div> Pools for the most part should be set to failmode=panic or wait, but a failed disk should not cause a panic. The system this happened to me on failmode was set to wait. It is also on r151012, waiting on a window to upgrade to r151014. My pool is raidz3, so no reason not to kick a bad disk.<o:p></o:p> </div> All my disks are SAS in DataON JBODs, dual connected across two LSI HBAs. BTW, pull a SAS cable and you get a panic too, not degraded multipath. Illumos seems to panic on just about any SAS event these days regardless of redundancy.<o:p></o:p> </div> -Chip<o:p></o:p> <div> <o:p> </o:p> <div> <o:p></o:p> </div> </div> </div> <div> <o:p> </o:p> <div> On Mon, May 18, 2015 at 3:08 PM, Paul B. Henson <<a href="mailto:henson@acm.org" target="_blank">henson@acm.org</a>> wrote:<o:p></o:p> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> On Mon, May 18, 2015 at 06:25:34PM +0000, Jeff Stockett wrote: > A drive failed in one of our supermicro 5048R-E1CR36L servers running > omnios r151012 last night, and somewhat unexpectedly, the whole system > seems to have panicked. You don't happen to have failmode set to panic on the pool? From the zpool manpage: failmode=wait | continue | panic Controls the system behavior in the event of catastrophic pool failure. This condition is typically a result of a loss of connectivity to the underlying storage device(s) or a failure of all devices within the pool. The behavior of such an event is determined as follows: wait Blocks all I/O access until the device connectivity is recovered and the errors are cleared. This is the default behavior. continue Returns EIO to any new write I/O requests but allows reads to any of the remaining healthy devices. Any write requests that have yet to be committed to disk would be blocked. panic Prints out a message to the console and generates a system crash dump.<o:p></o:p> <div> <div> _______________________________________________ OmniOS-discuss mailing list <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><o:p></o:p> </div> </div> </blockquote> </div> <o:p> </o:p> </div> </div> </body> </html>