I am archiving a vast amount of media files that are rarely accessed. I’m writing large sequential files, at peaks of about 100MB/s.
I want to maximise storage space primarily; I have 20x 18TB HDDs.
I’ve been told that large (e.g. 20 disk) vdevs are bad because resilvers will take a very long time, which creates higher risk of pool failure. How bad of an idea is this?
Draid mitigates a lot of the problems of very wide raidz
https://openzfs.github.io/openzfs-docs/Basic Concepts/dRAID Howto.html
Draid was released just a month after I built my last raid set with vdevs. Really hoping there’s an in-place migration path someday, assuming nobody finds any bugs in the next couple years.
Draid removes the capability of variable stripe widths, however. Strongly recommend a special metadata device when doing draid with the same level of redundancy as the rest of the pool.
If you have lots of small files, yes this is bad.
For videos the space lost will just be a rounding loss.
Would be interesting to test for music. A 100k 20mbyte files. You could lose a lot of space if using 1 mbyte+ stripes that have been recommended for a while now.