Best Practise - dataset configuration for PHOTO and IMAGE files

[Stux]

@winnielinnie

In defense of large recordsize (i.e, 1 MiB), I use it for all my pure storage / archival datasets.

There is also this.

Optimal drive layout for 14x NVMe, enterprise level

I’d like to accentuate that creating wider vdev does not automatically mean you get better space efficiency. It is true only if you have blocks (and files) big enough for each device in the vdev to get at least 8KB or better 32KB after compression. So in case of 8-wide RAIDZ1 you’d better have block sizes after compression of at least 256KB. Just last week I’ve had couple cases when user put ZVOL with 32KB volblocksize onto 9-wide RAIDZ2, as result getting both worst possible IOPS, highest po…

Seems to me that if you’re using wide raidz you may want to increase record size too.

The record size is BEFORE compression right?