Anyone planning on ZFS or BTRFS for file systems?

[Arwen]

...
There are ways that BTRFS can loose data. It's not a totally COW;

https://btrfs.wiki.kernel.org/index.php/..._rename.3F

For home use, I'd not worry about it. But, for data center use, (in reference to BTRFS in general, not BTRFS on Pinebook Pro), I'd consider this un-acceptable.

Oh, I forgot another way BTRFS and ZFS differ, BTRFS stores the checksum with the blocks, (data or metadata).

ZFS stores the checksum in the parent block. So that means ZFS stores data block checksums with the directory entries' metadata, and the directories' checksum with it's parent directory. And the root level directory in the Uber block, (top level file system descripter).

This difference is not too important until you run across mis-written data. (Probably so rare, most people never even heard of it.) With BTRFS, a scrub of the data may not detect this. But, ZFS would. Again, not to important for home use. And I'd return to using BTRFS on a Pinebook Pro without hesitation if ZFS was not usable on ARM64.

This became important to me when I selected the first 8TB disk of reasonable price, the Seagate Archive SMR, (Shingled Magnetic Recording). This type of disk ALWAYS relocates data blocks on write, (somewhat like flash does). Using ZFS was a no-brainer on that disk. It gave me both data validation, (for the more complex firmware Seagate had to use), and snapshots so I can store and release incremental backups easily.