问题原文
原帖链接 · brianclements · CC BY-SA 4.0
I've have a ext4 on LVM on linux RAID based NAS for a decade + that runs syncthing and syncs dozens of devices in my homelab. Works great. I'm finally building it's replacement based on ZFS RAID (first experience with ZFS), so lots of learning.
I know that:
- Dedup is a good idea in very few cases (I'm aware of the RAM implications. Let's assume I wait until fast-dedup stabilizes and makes it into my system)
- That most of my syncthing activity is little modifications to existing files
- That random async writes are harder/slower on a zraid2. Syncthing would be everpresent but the load on the new NAS would be light otherwise.
- Syncthing works by making new files then deleting the old one by default, but maybe copy_file_range changes this?
My questions are:
- seeing how ZFS is COW, and syncthing would just constantly be flooding the array with small random writes to existing files, isn't it more efficient to make a dataset out of my syncthing data and enable dedup there only?
- How does this syncthing setting interact with the ZFS dedup settings? copy_file_range Would it override the ZFS setting or do they both need to be enabled?
Update: Version info (Probably):
- Ubuntu 22.04 or 24.04
- kernel 6.5+
- syncthing 1.27.5
- OpenZFS 2.3
社区高分解答
原帖链接 · BaronSamedi1958 · CC BY-SA 4.0
ZFS deduplication isn't the sharpest tool in the shed... It's memory hog and it chews into read IOPS which aren't great for RAIDZx. If you absolutely need dedupe for whatever scenario you have (file server I guess?) you'd better go with virtualization and enable OS-level dedupe (VDO for Linux and whatever-Microsoft-calls-it-this-week for Windows Server). We run a couple of Proxmox+ZFS hosts doing exactly this and are quite happy with perf (KVM), reliability (ZFS), and space savings (VDO). Good luck!
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
