Today I learned that btrfs has an option to cache metadata to SSD. Let alone itâs first visible on synology.
from otherâs experience with zfs, having metadata on a fast SSD (either as a cache or exclusively) should help storj a ton with things like used space filewalkers and garbage collection.
And itâs cool because plain btrfs performance with storj is quite poor.
Yes. Itâs quite interesting how Synology made it work. And why they strongly recommend btrfs over ext4? Overall, Pin all BTRFS metadata to SSD cache works like a charm. Wonder why are folks not using it outside of Synology?
Because itâs also required to modify BTRFS (Iâm not sure that Synology published their improvements to the upstream - BTRFS is a Open Source project).
BTRFS repair function works good only in RAID setup (otherwise there is no way to recover a broken data - no other source), but the native BTRFS RAID is a mess. Thus Synology uses MD RAID for that. But, the filesystem should have a knowledge about this fact to be able to autoheal. So, Synology patched BTRFS to be aware of the fact that itâs running in the RAID and can use the auto repair function on case of CRC failure.
But other implementations with MD can use SSD as a cache layer too, as an LVM. But without patched BTRFS it doesnât make sense to use BTRFS in LVM or MD RAID, because the auto repair BTRFS function wouldnât be aware of the RAID. If you need that function, then the only choice is ZFS (or Synology ). ZFS also can use SSD in many variations (much more than LVM or MD for example) and have an auto repair function out of the box (of course only in RAID setup with mirror or parity).