13:39:12 [illumos-gate] 18377 hma conflates CPU ID with sequence ID -- Andy Fiddaman 13:50:12 well that was annoying... 13:50:43 maybe because the window was open, but redmine seems to have eating my bug 13:57:52 guess i'll try again... 13:58:22 there we go 13:58:29 people might be interested in this one... 14:37:16 huh 14:39:56 fenix illumos#18384 perhaps ? 14:39:58 BUG 18384: ZFS autotrim can corrupt pool (New) 14:39:58 ↳ https://www.illumos.org/issues/18384 14:50:47 yeah 14:51:16 (just turn it off if you have it on).... you probably won't hit it though unless your pool is really busy 14:51:39 since you need it busy enough that the TRIM I/Os end up sitting in the scheduler for at least a little bit 14:52:15 (and a full enough pool that zfs will want to allocate from the metaslab it just re-enabled moments ago vs. one of the others in the pool that weren't disabled) 14:52:33 i'll try to get the fix up in a bit 14:52:48 though I'm not sure about reproducing this -- it was found while looking for another issue 14:53:14 but also I think it's one of those that'd also be correct by inspection based on the earlier fix 15:29:36 wiedi_: hwgrok compiled, but for a bunch of my machines the drive bay info doesn't parse right 15:29:43 its lame. 15:29:49 sad :/ 15:30:46 since it should all come from the same place, does it also show up wrong in diskinfo? 15:38:31 probably.. IIRC diskinfo ultimately uses the same topo enumerators 18:33:09 yeah its some issue with my /dev/es/ses devices 18:33:23 i compiled and installed sg3_utils which does get the correct info 19:22:37 On that note, this is a weird error: cannot set property for 'rpool': property 'autotrim'(31) not defined 19:22:55 for got to pfexec the zpool command but certainly not the error I was expecting 19:35:27 maybe pool needs updating?