> From: Dan McDonald
> Sent: Tuesday, June 6, 2017 6:48 PM
>
> Shit, you're right:
I went ahead and updated the warning I had put on the wiki to clarify that
the bug only applies to 4k logical sector disks. I'm not sure how common
those are? Hopefully it will keep anybody else from unexpectedly
On Tue, Jun 06, 2017 at 08:54:00PM -0400, Dan McDonald wrote:
> Sorry for the VERY long latency. Started Joyent last week, attended a
> funeral yesterday, and more.
Congrats on the new job; my condolences on the funeral :(.
> The INTEL drives are 512b sectors. The HGST drives (which are NOT
>
> On Jun 6, 2017, at 9:47 PM, Paul B. Henson wrote:
>
> echo ::sd_state | mdb -k | egrep '(^un|_blocksize)'
Shit, you're right:
(2)# echo ::sd_state | mdb -k | egrep '(^un|_blocksize)'
un 0: ff0d0c58d9c0
un_sys_blocksize = 0x200
un_tgt_blocksize = 0x200
> On Jun 4, 2017, at 11:00 PM, Paul B. Henson wrote:
>
>>
>> And what does the "native" mean: is that "4kB physical AND 4kB logical
>> block size" as opposed to "4kB physical with 512B logical block size"?
>
> At this point I'm thinking the loader is only broken for disks
On Thu, Jun 01, 2017 at 01:01:49PM -0700, Paul B. Henson wrote:
> > From: Geoff Nordli
> > Sent: Tuesday, May 30, 2017 7:57 PM
> >
> > Right, it will not boot after upgrading to the new loader; even if the
> > 4K disks are not part of the rpool.
>
> Yikes 8-/, I'm glad I hadn't got around to
> From: Geoff Nordli
> Sent: Tuesday, May 30, 2017 7:57 PM
>
> Right, it will not boot after upgrading to the new loader; even if the
> 4K disks are not part of the rpool.
Yikes 8-/, I'm glad I hadn't got around to updating; my data pool consists
of 13 WD Red 3TB drives which are 4K native. I'm
For what it’s worth I’ve seen the same error message on a Dell server that
happened to have 10TB-drives (not the boot disks!) that was formatted using
4104-bytes sectors in order to support the T10-PI/DIF & T10-DIF standards. The
errors started to occur when we replaced the RAID controller with
On 2017-05-18 01:06 PM, Dan McDonald wrote:
On May 18, 2017, at 3:55 PM, Geoff Nordli wrote:
Hi.
I upgraded to the latest r151022 version. The upgrade went fine, rebooted the
machine, then upgraded to the new loader.
When i rebooted after the loader upgrade, I got an