On Apr 29, 2012, at 11:45 AM, George Wilson wrote: > > On Apr 29, 2012, at 1:28 PM, Roy Sigurd Karlsbakk wrote: > >>>> Also, I posted a bug report for it here >>>> https://www.illumos.org/issues/2663 >>> >>> Thanks :-). We can now track the progress of the OI-specific >>> discussion about this issue. >> >> Seems the old post about the initial patch is here >> https://www.illumos.org/issues/453 >> >> After som discussion on #openindiana (irc.freenode.net), it seems the best >> would perhaps be to port the ashift flag available in Linux. Also, some SSDs >> might need ashift=13 for optimal performance… >> >> Vennlige hilsener / Best regards >> >> roy >> -- >> Roy Sigurd Karlsbakk >> (+47) 98013356 >> r...@karlsbakk.net >> http://blogg.karlsbakk.net/ >> -- >> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det >> er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av >> idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate >> og relevante synonymer på norsk. >> >> _______________________________________________ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > Speaking of 4K sectors, I've taken a slightly different approach that fixes > this outside of ZFS. The idea is to allow sd to override the > physical-block-size which ZFS will pick up. The way this works is you can > specify the Vendor/Product id in sd.conf. Here's an example: > > sd-config-list = "NETAPP LUN, "physical-block-size:4096";
This is the preferred solution and there are several implementations running around in various stages of test/release/acceptance. I look forward to getting this upstream :-) -- richard -- ZFS Performance and Training richard.ell...@richardelling.com +1-760-896-4422 _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
