Update:
I was too scared to completely delete my original pool even though I made a second pool (one 10TB disk) with a copy of all the media files.
Instead, I detached 4 of the drives from the original pool since everything was mirrored. This leaves me with 2 copies of all of the data while I mess around with the 4 unused disks (3 HDDs and 1 SSD)
I created a new pool with 3 data disks striped together and 1 special vdev but the SSD stayed at 4k and not the native 8k bit sector. Then I removed the special vdev (which I guess was ok since there was no data in the pool?) and wiped it. I tried adding it through the GUI as a special vdev, but it still retained the 4k size and gave me a warning when I did ZPOOL STATUS.
So I removed the SSD from the pool again and re-added it through the CLI.
zpool add -o ashift=13 fishpond special /dev/da5
And that worked!
children[4]:
type: 'disk'
id: 4
guid: 6524976860394182817
path: '/dev/da5'
whole_disk: 1
metaslab_array: 157
metaslab_shift: 30
ashift: 13
asize: 200044707840
is_log: 0
create_txg: 307
com.delphix:vdev_zap_leaf: 771
com.delphix:vdev_zap_top: 772
I still need to calculate what the small block size should be, but luckily I found the webpage that I was thinking of:
forum.level1techs.com
Once I figure out the small block size, then I will destroy the original pool and attach those 4 drives as mirrors into my newest pool.
I was too scared to completely delete my original pool even though I made a second pool (one 10TB disk) with a copy of all the media files.
Instead, I detached 4 of the drives from the original pool since everything was mirrored. This leaves me with 2 copies of all of the data while I mess around with the 4 unused disks (3 HDDs and 1 SSD)
I created a new pool with 3 data disks striped together and 1 special vdev but the SSD stayed at 4k and not the native 8k bit sector. Then I removed the special vdev (which I guess was ok since there was no data in the pool?) and wiped it. I tried adding it through the GUI as a special vdev, but it still retained the 4k size and gave me a warning when I did ZPOOL STATUS.
So I removed the SSD from the pool again and re-added it through the CLI.
zpool add -o ashift=13 fishpond special /dev/da5
And that worked!
children[4]:
type: 'disk'
id: 4
guid: 6524976860394182817
path: '/dev/da5'
whole_disk: 1
metaslab_array: 157
metaslab_shift: 30
ashift: 13
asize: 200044707840
is_log: 0
create_txg: 307
com.delphix:vdev_zap_leaf: 771
com.delphix:vdev_zap_top: 772
I still need to calculate what the small block size should be, but luckily I found the webpage that I was thinking of:
ZFS Metadata Special Device: Z
Introduction ZFS Allocation Classes: It isn’t storage tiers or caching, but gosh darn it, you can really REALLY speed up your zfs pool. From the manual: Special Allocation Class The allocations in the special class are dedicated to specific block types. By default this includes all metadata...
forum.level1techs.com
Once I figure out the small block size, then I will destroy the original pool and attach those 4 drives as mirrors into my newest pool.
