WRT sensitivity is note #3 here inaccurate?
https://www.illumos.org/issues/2665#note-3
As an example, here is a device that is particularly problematic...
The HDS721010DLE630 which reports itself to the OS as vid = "ATA " and pid
= "Hitachi HDS72101" which should be handled by the following in sd.conf
sd-config-list =
"ATA HITACHI HDS72101", "physical-block-size:4096";
However, it isn't. Nor is it caught by any amount of wildcarding around all
or portions of those ID strings. Pools create stubbornly at ashift 9.
Any advice?
-mjf
On Wed, Aug 21, 2013 at 12:17 AM, Richard Elling <
richard.ell...@richardelling.com> wrote:
>
> On Aug 20, 2013, at 6:40 PM, Matthew Frazer <mattfra...@gmail.com> wrote:
>
> This is a question I've been meaning to ask as well.
>
> Using the information at
> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks I've
> edited the sd.conf on my systems to include the drives I wish to have 4k
> sector sizes on. On Solaris 11.1 this achieves the proper ashift on 4k
> drives whether they report 4k or 512e to the system. The same sd.conf does
> not, at least in my experience, result in an ashift of 12 on OmniOS. My
> workaround has been to create my pools in 11.1 with version flags set
> compatible to what omnios supports, then import them into OmniOS and then
> zfs upgrade them. I'd love to find out I've been doing it wrong as it would
> simplify pool creation greatly for me.
>
> The file is very sensitive to spaces and format, including separators.
> Make sure you
> have the file exactly as needed.
> -- richard
>
> --
>
> richard.ell...@richardelling.com
> +1-760-896-4422
>
>
>
>
--
It is in love that we are made, in love we disappear.
-Leonard Cohen
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
