this post was submitted on 17 Feb 2025
3 points (100.0% liked)
Everything ZFS
298 readers
3 users here now
A community for the ZFS filesystem.
ZFS is an opensource COW filesystem used by enterprise and serious homelabbers for it's data safety and extensive feature set.
OpenZFS is the active branch now developed primarily for Linux with a port to it's FreeBSD roots.
This community is here to answer questions and discuss topics related to the use of ZFS in the wild.
Rules:
As always, the main rule is Don't Be a Dick. Be polite with new users asking questions that you may consider obvious. If you don't have something constructive to offer, downvote and move on.
No dirty deletes: your posts are here for posterity, perhaps the next person will get something out of it, even if it's wrong.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No. I think you're misunderstanding the concept though. You're not "offloading" portions of a pool to something and acting as cache, you're just moving portions of the functioning pool to elsewhere. Of course you lose your pool if these die, because they ARE the pool.
This kind of setup isn't really meant to be super useful for a single pool configuration like yours, and I doubt you'd see a gigantic performance improvement. You'd see more drastic improvements if you were running dozens of HDDs running multiple pool partitions per drive and then added SSDs as metadata devices.
Thanks for the reply. That is my understanding. That it's basically expanding the pool, and hence has same redundancy/backup requirements. I was wondering if it's possible to set up a metadata cache. From the replies, it seems like that's not possible for ZFS.
I've never heard of such a thing, and not even sure how that would work.