@mhamzahkhan Nope but a home enthusiast is curious to hear your conundrum 😅
I actually just finished installing Arch with ZFS root on my laptop tonight. First time doing it on a "workstation".

@michael well, basically I have a simple 4xdrive zpool, which is stripped and mirrored (paste.centos.org/view/f1d512c2). All 4 disks are the same SSD models, but when I originally created the pool, I accidentally created one vdev with ashift=12, whereas the other one is ashift=13.


@michael I wanted to correct it so both vdevs have the same ashift value. Initially, I was hoping to break the mirrors so temporarily convert the pool to effectively RAID0 across 2 SSDs, then add a new mirrored vdev, with the correct ashift value (13), then remove the incorrect vdev, and re-add that SSD to the remaining single disk vdev.
If that makes sense?

But from a bit of reading, it seems I can't do that since you can't decrease the size of a zpool. So my only option is to just re-create.

@mhamzahkhan Looks like it's possible on actual Solaris ZFS.


But don't know if zpool remove is implemented in OpenZFS, I'm not at a terminal to check.

@mhamzahkhan Hmm if "sector size" and "ashift" are interchangeable in this context, you might be borked. Which after reading the first article I linked and the bits about copying to a virtual vdev hosted on the remaining vdevs, kind of makes sense.


@michael I'll just re-create it when I have some time. It's not a huge array, only slightly more than 100GB or so in use that is "important" to me.
It's mainly used as storage for my homelab K8S cluster, so I didn't want to bring it down to re-create if I could get away with it 😂

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!