Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: some zfs fine tuning #448

Merged
merged 1 commit into from
Jan 2, 2025
Merged

docs: some zfs fine tuning #448

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/zfs-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,10 +48,22 @@ A good cheat-sheet: https://blog.mikesulsenti.com/zfs-cheat-sheet-and-guide/

* [`zdb`](https://openzfs.github.io/openzfs-docs/man/master/8/zdb.8.html) is also worth knowing (`zdb -s <poolname>` for example)

## Some Fine-Tuning

We use compression on a lot of our datasets (`compression=on`).

You can set `primarycache=metadata` for volumes with large number of files,
that are not critical to read fast. (eg. Images on off container, or backups from other servers).

In [Munin](./munin.md) `ZFS ARC - Hit ratio` the `ZFS Arc Efficiency` gives you an idea of how well ZFS caching is performing.


## Proxmox

Proxmox uses ZFS to replicate containers and VMs between servers. It also use it to backup data.

Note: we progressively abandon Proxmox ZFS replication in favor of using sanoid/syncoid.

## Using sanoid

We use sanoid / syncoid to sync ZFS datasets between servers (also to back them up).
Expand Down
Loading