I am interested in ZFS properties that are problematic to redefine after the creation of zpool/datasets (such as compression property, the effect of which will not apply retrospectively).
It's funny, but I've been using FreeBSD and ZFS for over 3 years now and creating zpool and datasets using the default properties. In the following way:
I didn't even set the compression property although it is known to have negligible CPU overhead, it saves significant disk space in some cases. Currently I do
And I create a dataset with the complession property:
Please, advise what properties should I pay attention to BEFORE creating a pool and datasets so as not to recreate these pools and increased writing on disks?
It's funny, but I've been using FreeBSD and ZFS for over 3 years now and creating zpool and datasets using the default properties. In the following way:
Code:
zpool create -m none test
zfs create test/test
I didn't even set the compression property although it is known to have negligible CPU overhead, it saves significant disk space in some cases. Currently I do
sysctl vfs.zfs.min_auto_ashift=12
before creating a pull (this is another pool-related setting that cannot be changed later).And I create a dataset with the complession property:
Code:
zfs create -o compression=lz4 test/test
Please, advise what properties should I pay attention to BEFORE creating a pool and datasets so as not to recreate these pools and increased writing on disks?