Hi Matt, The ashift is a property of vdevs at the top of the configuration tree. It is not of a property of the vdevs below mirrors and raidz vdevs. So replacing a drive in a mirror or raidz vdev won't affect this property.
I also have a suspicion that you can't change the ashift without recreating the pool. A spacemap with a larger ashift would not be able to describe the closely packed allocations in a vdev with a smaller ashift. So increasing the ashift would require rewriting all the blocks and block pointers to fit in the coarser allocation granularity. I don't believe this block pointer rewrite code exists yet. Regards, Austin On Sat, Mar 15, 2014 at 2:53 PM, Matt Connolly <[email protected]> wrote: > Dear list, > > I’ve just replaced a drive in a zpool with ashift=9 with a new drive that > has 4k sectors. > > I’ve read through several instructional pages and I cannot override the > size by editing the /kernel/drv/sd.conf file, according to: > > http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks > http://blog.delphix.com/gwilson/2012/11/15/4k-sectors-and-zfs/ > > Is the following feature included in the SmartOS live kernel? > > https://www.illumos.org/issues/2665 > > Perhaps it is and it only supports making block sizes larger, not smaller? > > > Thanks > Matt > > *smartos-discuss* | > Archives<https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/25735310-6b6dced1> | > Modify<https://www.listbox.com/member/?&;>Your Subscription > <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
