I applied zfs_fallocate_reserve_percent=0 to the kernel module, confirmed it was set, but I still see the same incorrect behavior with fallocate:
root@nsn7:/tank/test# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls -lah foo.img -rw-r--r-- 1 root root 0 abr 19 10:35 foo.img
root@nsn7:/tank/test# uname -a Linux nsn7 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@nsn7:/tank/test# cat /sys/module/zfs/parameters/zfs_fallocate_reserve_percent 0
I applied zfs_fallocate_ reserve_ percent= 0 to the kernel module, confirmed it was set, but I still see the same incorrect behavior with fallocate:
root@nsn7: /tank/test# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls -lah foo.img
-rw-r--r-- 1 root root 0 abr 19 10:35 foo.img
root@nsn7: /tank/test# uname -a
Linux nsn7 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@nsn7: /tank/test# cat /sys/module/ zfs/parameters/ zfs_fallocate_ reserve_ percent
0