Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

1.3K

Fascinating idea imo. Could bring life to some of the throw away SSDs you might have to slap in between you and your spin backup drive.

Fascinating idea imo. Could bring life to some of the throw away SSDs you might have to slap in between you and your spin backup drive.

(post is archived)

[–] • 3 pts

ZFS can do that, it can even use different read and write cache.

[–] • 0 pt

You think it's better than Bcachefs?

[–] • 1 pt

Feature wise it is, but in your use case it might be overkill.

[–] • 1 pt

Bcachefs is sus because supposedly it's made by a google employee.

[–] • 1 pt

Bcachefs only performs a subset of what ZFS can do. ZFS is generalized and is very heavy in comparison for resource requirements. Bcachefs is also very young (admittedly a couple years since I last looked at it) in comparison. "Better" is probably not the question to ask.

[–] • 2 pts (edited )

intel optane and amd storemi software does this. earliest software that comes to mind was readyboost shit they offered in vista that used a usb drive to supplement ram. Ofc linux had it's cache and journaling file systems long b4 you're watching a better hardware tuned evolution of that

[–] • 1 pt

CEPH.

[–] • 0 pt

... a file system that I routinely DOS with a fucking mv command 🤣.

[–] • 1 pt

Not filesystems, but device-level tools that can work with any filesystem:

LVM cache. I tried it a few months ago and it seemed to properly wait until something was read multiple times before putting it in the cache. It didn't seem to cache writes (which was good for my use).

bcache, but it didn't seem to allow disabling write caching. So every useless log file of web browser write would go through the SSD, even if it's never read again.

I finally just gave up and split filesystems. Boot entirely on SSD, home on HDD. With a few exceptions from /var being put on HDD using mountpoints in fstab.

[–] • 0 pt

just a thought, but there are different disk writing algorithms that you can implement and tune within your kernel that will use RAM as your write cache. (so long as you're using Linux)

[–] • 0 pt

For writing I would have assumed it already did use ram to cache. Maybe not so much for later rereading.

I forget exactly what but I could have sworn there was a command for preloading a file into memory.

[–] • 1 pt

yep. In fact, if you've recently worked with it, the OS doesn't have to reload it from disk. And, depending upon how you tune the kernel you could make it to where the OS practically only ever flushes the disk writes upon reboot or exceeding physical memory. until that point all work with the file is being performed within in the memory space.

[–] • 0 pt

I splurged and bought WD Red Pros and they'll last for 114 years.

[–] • 0 pt

How did you calculate 114?

[–] • 0 pt

They say the MTBF is 1,000,000 hours.

[–] • 0 pt

...one of my multiple 8 disk raid 6's is comprised of WD reds. i've already experienced 3 failures. this raid is less than 4 years old, and lightly used. may not want to believe those marketing claims.

[–] • 0 pt

I've been using mine for 6 years now.

[–] • 0 pt

I've got a 12TB. 2 TB in use now.