On 20 September 2016 at 07:00, InterNetX - Juergen Gotteswinter
wrote:
> try changing this in /kernel/drv/sd.conf
> sd-config-list=
> "",
> "retries-timeout:1,retries-busy:1,retries-reset:1,retries-victim:2,physical-blocksize:4096",
This is not likely to help. The
> On Sep 20, 2016, at 6:48 AM, Humberto Ramirez wrote:
>
> Is there a definitive approach / guide / manual / wiki as to how to properly
> work / replace 4k - 512 - 512e disks? This has been asked before, here and in
> some other lists and obviously continues to be a source
update_drv -vf sd
sorry, typo
Am 20.09.2016 um 16:00 schrieb InterNetX - Juergen Gotteswinter:
> try changing this in /kernel/drv/sd.conf
>
> sd-config-list=
> "",
> "retries-timeout:1,retries-busy:1,retries-reset:1,retries-victim:2",
>
>
> to
>
> sd-config-list=
> "",
>
try changing this in /kernel/drv/sd.conf
sd-config-list=
"",
"retries-timeout:1,retries-busy:1,retries-reset:1,retries-victim:2",
to
sd-config-list=
"",
"retries-timeout:1,retries-busy:1,retries-reset:1,retries-victim:2,physical-blocksize:4096",
and if any of the other entries
Is there a definitive approach / guide / manual / wiki as to how to
properly work / replace 4k - 512 - 512e disks? This has been asked before,
here and in some other lists and obviously continues to be a source of
problems and confusion...
On Sep 19, 2016 11:54 PM, "Joshua M. Clulow"
Hi Joshua
Thank you very much!
The original disk driver just report logical sector size 512 byte without a
physical sector size. We create the zpool with default setting.
And zfs use logical sector size as ashift if physical sector size do not
reported.
The replacement disk is a different model
Hi all,
I have created an zpool with ashift=9.
Now a disk is out of service. And I try to replace with a new disk.
Unfortunately, new disk reports that the physical sector size is 4k. Some error
occurs when trying exec command “zfs replace”/ “zfs attach”.
[cid:image001.png@01D2132F.F04C7960]