From 9952c58a4a09db92e0f07ccae003f46cc8fc3b54 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Tue, 4 Feb 2020 11:06:51 -0500 Subject: [PATCH] add links to ZFS comparison --- README.md | 2 +- man/mergerfs.1 | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index b7f2365e..12a4c5ad 100644 --- a/README.md +++ b/README.md @@ -1021,7 +1021,7 @@ When combined with something like [SnapRaid](http://www.snapraid.it) and/or an o #### Why use mergerfs over ZFS? -MergerFS is not intended to be a replacement for ZFS. MergerFS is intended to provide flexible pooling of arbitrary drives (local or remote), of arbitrary sizes, and arbitrary filesystems. For `write once, read many` usecases such as bulk media storage. Where data integrity and backup is managed in other ways. In that situation ZFS can introduce major maintenance and cost burdens as described [here](http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-nas.html). +MergerFS is not intended to be a replacement for ZFS. MergerFS is intended to provide flexible pooling of arbitrary drives (local or remote), of arbitrary sizes, and arbitrary filesystems. For `write once, read many` usecases such as bulk media storage. Where data integrity and backup is managed in other ways. In that situation ZFS can introduce a number of costs and limitations as described [here](http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-nas.html), [here](https://markmcb.com/2020/01/07/five-years-of-btrfs/), and [here](https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNoRealReshaping). #### What should mergerfs NOT be used for? diff --git a/man/mergerfs.1 b/man/mergerfs.1 index dbd27ad2..915540c6 100644 --- a/man/mergerfs.1 +++ b/man/mergerfs.1 @@ -2126,9 +2126,11 @@ MergerFS is intended to provide flexible pooling of arbitrary drives For \f[C]write\ once,\ read\ many\f[] usecases such as bulk media storage. Where data integrity and backup is managed in other ways. -In that situation ZFS can introduce major maintenance and cost burdens -as described -here (http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-nas.html). +In that situation ZFS can introduce a number of costs and limitations as +described +here (http://louwrentius.com/the-hidden-cost-of-using-zfs-for-your-home-nas.html), +here (https://markmcb.com/2020/01/07/five-years-of-btrfs/), and +here (https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNoRealReshaping). .SS What should mergerfs NOT be used for? .IP \[bu] 2 databases: Even if the database stored data in separate files (mergerfs