![]() While, yes, properly tweaking ZFS for performance and making proper decisions on things like recordsizes, L2ARC and SLOG requires a bit of deeper understanding of how it works, the CLI is very approachable and the man pages are straight-forward and easy to understand for a beginner.Ĭompared the alternatives of cryptsetup/mdadm/lvm/lvcache, it's such a breath of fresh air and a lot easier to work with. * create a dataset (persistently mounted across reboots, with optional encryption and compression etc) I've been aware of and thinking to check out ZFS for over a decade because all these weird nerds keep talking about it but it seemed so involved and complicated. Although that was an adventure on its own.Īgreed. I know BTRFS also attempts to provide this, and there's the licensing issues with ZFS, but I wanted MacOS compatibility also. And it all comes with things I didn't know I needed, like filesystem compression. I run datasets for categories of data and I can choose categories that I want regular local snapshots of (zvol/crypt/Documents, zvol/crypt/scripts, zvol/crypt/Papers)Įssentially, ZFS manages my files for me. Not to mention being able to snapshot important folders to the native drive in case I need to recover a file from a previous state. Now being able to plug a drive in and take a snapshot without rsyncing or thinking about what I'm snapshotting, having it be inherent to the filesystem, was a game changer. ![]() I've been a linux user for 13 years but never felt the need to have a fileserver. for me using ZFS has changed the way I look at files, filesystems, data, and backups for general computing. You know, these articles always come up in the context of fileservers but.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |