<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 14 (filtered medium)"> <style></style> </head> <body lang="EN-GB" link="blue" vlink="purple"> <div class="WordSection1"> They are failed as far as OmniOS is concerned, from what I can tell:<o:p></o:p> <o:p> </o:p> Jun 08 01:08:54 710768e8-2f2b-4b3d-9d4b-a85ef5617219 DISK-8000-12 Major<o:p></o:p> <o:p> </o:p> Host : 2hus291<o:p></o:p> Platform : S5500BC Chassis_id : ............<o:p></o:p> Product_sn :<o:p></o:p> <o:p> </o:p> Fault class : fault.io.disk.over-temperature<o:p></o:p> Affects : dev:///:devid=id1,sd@n5000c5007242271f//scsi_vhci/disk@g5000c5007242271f<o:p></o:p> faulted and taken out of service<o:p></o:p> FRU : "Slot 21" (hc://:product-id=LSI-SAS2X36:server-id=:chassis-id=500304800033213f:serial=S1Z02A8M0000K4361NF4:part=SEAGATE-ST4000NM0023:revision=0003/ses-enclosure=1/bay=20/disk=0)<o:p></o:p> faulty<o:p></o:p> <o:p> </o:p> Description : A disk's temperature exceeded the limits established by<o:p></o:p> its manufacturer.<o:p></o:p> Refer to http://illumos.org/msg/DISK-8000-12 for more<o:p></o:p> information.<o:p></o:p> <o:p> </o:p> root@2hus291:/root# zpool status pool0<o:p></o:p> pool: pool0<o:p></o:p> state: DEGRADED<o:p></o:p> status: One or more devices is currently being resilvered. The pool will<o:p></o:p> continue to function, possibly in a degraded state.<o:p></o:p> action: Wait for the resilver to complete.<o:p></o:p> scan: resilver in progress since Tue Jun 9 11:11:16 2015<o:p></o:p> 18.8T scanned out of 91.7T at 667M/s, 31h48m to go<o:p></o:p> 591G resilvered, 20.55% done<o:p></o:p> config:<o:p></o:p> <o:p> </o:p> NAME STATE READ WRITE CKSUM<o:p></o:p> pool0 DEGRADED 0 0 0<o:p></o:p> raidz2-0 DEGRADED 0 0 0<o:p></o:p> c0t5000C50055ECA49Bd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055ECA4B3d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055ECA587d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055ECA6CFd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055ECA7F3d0 ONLINE 0 0 0<o:p></o:p> spare-5 REMOVED 0 0 0<o:p></o:p> c0t5000C5007242271Fd0 REMOVED 0 0 0<o:p></o:p> c0t5000C50055EF8A6Fd0 ONLINE 0 0 0 (resilvering)<o:p></o:p> c0t5000C50055ECAB23d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055ECABABd0 ONLINE 0 0 0<o:p></o:p> raidz2-1 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EE9D87d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EE9E43d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EEA5ABd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EEBA5Fd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EEC1E3d0 ONLINE 0 0 0<o:p></o:p> c0t5000C500636670BFd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EF8CBBd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055EF8D33d0 ONLINE 0 0 0<o:p></o:p> raidz2-2 ONLINE 0 0 0<o:p></o:p> c0t5000C50055F7942Fd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055F79E03d0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055F7A8DFd0 ONLINE 0 0 0<o:p></o:p> c0t5000C50055F81C1Bd0 ONLINE 0 0 0<o:p></o:p> c0t5000C5005604A42Bd0 ONLINE 0 0 0<o:p></o:p> c0t5000C5005604A487d0 ONLINE 0 0 0<o:p></o:p> c0t5000C5005604A74Bd0 ONLINE 0 0 0<o:p></o:p> c0t5000C5005604A91Bd0 ONLINE 0 0 0<o:p></o:p> raidz2-4 DEGRADED 0 0 0<o:p></o:p> c0t5000C500562ED6A3d0 ONLINE 0 0 0<o:p></o:p> c0t5000C500562F8DEFd0 ONLINE 0 0 0<o:p></o:p> c0t5000C500562F92D7d0 ONLINE 0 0 0<o:p></o:p> c0t5000C500562FA0DFd0 ONLINE 0 0 0<o:p></o:p> c0t5000C500636679EBd0 ONLINE 0 0 0<o:p></o:p> spare-5 DEGRADED 0 0 14<o:p></o:p> c0t5000C50057FBB127d0 REMOVED 0 0 0<o:p></o:p> c0t5000C5006366906Bd0 ONLINE 0 0 0<o:p></o:p> c0t5000C5006366808Fd0 ONLINE 0 0 0<o:p></o:p> spare-7 REMOVED 0 0 0<o:p></o:p> c0t5000C50057FC84F3d0 REMOVED 0 0 0<o:p></o:p> c0t5000C50063669937d0 ONLINE 0 0 0<o:p></o:p> logs<o:p></o:p> mirror-3 ONLINE 0 0 0<o:p></o:p> c13t5003048000308398d0 ONLINE 0 0 0<o:p></o:p> c13t5003048000308399d0 ONLINE 0 0 0<o:p></o:p> cache<o:p></o:p> c13t5E83A97000005BC3d0 ONLINE 0 0 0<o:p></o:p> spares<o:p></o:p> c0t5000C5006366906Bd0 INUSE currently in use<o:p></o:p> c0t5000C50063669937d0 INUSE currently in use<o:p></o:p> c0t5000C50055EF8A6Fd0 INUSE currently in use<o:p></o:p> c0t5000C5006366994Bd0 AVAIL<o:p></o:p> <o:p> </o:p> Seems to be this that’s got me:<o:p></o:p> <o:p> </o:p> <a href="http://www.bigdatajunkie.com/index.php/10-hardware/19-seagate-constellation-es-3-firmware-0003">http://www.bigdatajunkie.com/index.php/10-hardware/19-seagate-constellation-es-3-firmware-0003</a> <o:p></o:p> <o:p> </o:p> Can’t interact with them unless I bring them ‘out of retirement’:<o:p></o:p> <o:p> </o:p> root@2hus291:/root# cat /etc/devices/retire_store<o:p></o:p> ▒ܱY^P"/scsi_vhci/disk@g5000c500724eacb70rio-store-version(rio-store-magic▒▒`(rio-store-flagsP"/scsi_vhci/disk@g5000c50057fbc1c30rio-store-version(rio-store-magic▒▒`(rio-store-flagsP"/scsi_vhci/disk@g5000c50057fbaf030rio-store-version(rio-store-magic▒▒`(rio-store-flagsP"/scsi_vhci/disk@g5000c50057fbb1270rio-store-version(rio-store-magic▒▒`(rio-store-flagsP"/scsi_vhci/disk@g5000c50057fc84f30rio-store-version(rio-store-magic▒▒`(rio-store-flagsP"/scsi_vhci/disk@g5000c5007242271f0rio-store-version(rio-store-magic▒▒`(rio-store-flags<o:p></o:p> <o:p> </o:p> Which, as I understand it, will necessitate a reboot. I’m going to try fwflash to see if I can get the firmware upgraded without having to pull all the disks and hook them up to a windows machine – has anyone else tried fwflash and Seagate disk firmware with any success? Fwflash seems to be able to see the disks, so I’m hopeful:<o:p></o:p> <o:p> </o:p> root@2hus291:/root# fwflash -l | grep ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> Product : ST4000NM0023<o:p></o:p> <o:p> </o:p> <a name="_MailEndCompose"><o:p> </o:p></a> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: OmniOS-discuss [mailto:omnios-discuss-bounces@lists.omniti.com] On Behalf Of Richard Elling Sent: 09 June 2015 20:17 To: Narayan Desai Cc: omnios-discuss@lists.omniti.com Subject: Re: [OmniOS-discuss] Zpool export while resilvering?<o:p></o:p> </div> </div> <o:p> </o:p> <o:p> </o:p> <div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> On Jun 9, 2015, at 12:00 PM, Narayan Desai <<a href="mailto:narayan.desai@gmail.com">narayan.desai@gmail.com</a>> wrote:<o:p></o:p> </div> <o:p> </o:p> <div> <div> You might also crank up the priority on your resilver, particularly if it is getting tripped all of the time:<o:p></o:p> <div> <a href="http://broken.net/uncategorized/zfs-performance-tuning-for-scrubs-and-resilvers/">http://broken.net/uncategorized/zfs-performance-tuning-for-scrubs-and-resilvers/</a><o:p></o:p> </div> <div> -nld<o:p></o:p> </div> </div> </div> </blockquote> <div> <o:p> </o:p> </div> <div> In general, yes this is a very good post. However, for more recent ZFS and certainly<o:p></o:p> </div> <div> the lastest OmniOS something-14 release, the write throttle has been completely<o:p></o:p> </div> <div> rewritten, positively impacting resilvers. And, with that rewrite, there is a few more<o:p></o:p> </div> <div> tunables at your disposal, while the old ones fade to the bucket of bad memories :-)<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> In most cases, resilver is capped by the time to write to the resilvering device.<o:p></o:p> </div> <div> You can see this in iostat "-x" as the device that is 100% busy with write workload.<o:p></o:p> </div> <div> That said, for this specific case, the drives are not actually failed, just taken offline,<o:p></o:p> </div> <div> so you could have a short resilver session, once they are brought back online.<o:p></o:p> </div> <div> -- richard<o:p></o:p> </div> <o:p></o:p> <div> <div> <div> <div> <div> >This is probably a silly question, but I¹ve honestly never tried this and >don¹t have a test machine handy at the moment can a pool be safely >exported and re-imported later if it is currently resilvering? > <o:p></o:p> </div> </div> </div> </div> </div> </div> <o:p> </o:p> </div> </body> </html>