3 ms·
Bcachefs supports both caching and tiering: https://wiki.archlinux.org/title/Bcachefs#SSD_caching https://wiki.archlinux.org/title/Bcachefs#SSD_caching A FUSE-
by rzzzt 1y ago
Bcachefs supports both caching and tiering: https://wiki.archlinux.org/title/Bcachefs#SSD_caching https://wiki.archlinux.org/title/Bcachefs#SSD_caching
A FUSE-based solution is autotier: https://github.com/45Drives/autotier https://github.com/45Drives/autotier
- riedel 1y agoLooked at Autotier before, but the development looked pretty stale (which is not too bad per se if it is stable). Is there any experience/ recommendations with putting bcachefs also on top of networked block storage such as CEPH ? As CEPH SSD caching seems pretty deprecated by default, at work we looked at a solution to marry our HDD and SSD pool for users that do want to put too much thoughts into tiering by mount points.
- magicalhippo 1y agoWill be interesting to play with. I used lvm cache to put ZFS on top of local NVMe for write-back caching of iSCSI targets, as ZFS has good built-in read caching. Worked pretty well in the limited tests I did, but it's not magic. Main reason I didn't pursue is that it felt a bit like a house of cards. Though on the positive side, one could always mount the underlying storage, ie partitions serving the iSCSI targets, as a local pool on another machine.
- IcePic 1y agoYou could use bcachefs on the OSD drives, but you can also just point the WAL/DB of the OSD to a partition on the ssd and have the data on hdd. You don't have to tier pools to get help with small writes/metadata using ssds.