16:14:59 [illumos-gate] 16282 libresolv2: left shift of negative value -- Toomas Soome 16:58:15 so, how do I make fmd make a fail LED light automatically when a drive dies? These drives have SES and I can manually set it via fmtopo -P but it turns itself off after like a minute 16:58:52 or rather this chassis + backplane has SES, independent of the drive. fmtopo also knows which drive is attached to which bay 16:59:28 It would seem all the right ingredients are here. And for all I know, when it was faulted it lit the drive but turned off the LED after a minute just like when I manually set the fail LED to on 17:00:08 it depends on how it fails 17:00:21 there are certain situations where it should do that already, but not all of them 17:00:30 though I can't recall the specifics offhand 18:20:15 one of the things one my list of stuff I'd like to do is add some code to the disk fma module to enable background scanning on disks that support it 18:21:44 we also interpret all read failures as a disk i/o failure.. there's a few of them though we should treat more like a checksum error, remap the LBA on the disk and let zfs self heal it 18:22:14 instead of treating it like the whole disk has gone bad 18:22:27 (at least where we can) 21:11:10 [illumos-gate] 16291 udapl: multiply-defined symbols -- Toomas Soome 21:46:45 jbk: fma in this case has marked the disk faulty 21:47:30 the pool faulted the device, fma generated an event, I suspect this is a case where the disk should have been marked as faulted by the LED 21:48:09 I also find it an interesting coincidence that setting the LED to fail manually only works temporarily, as if the backplane wants the SAS controller / software to constantly assert the fault 21:56:18 [illumos-gate] 16332 AVX-512 VBMI dis support -- Robert Mustacchi