All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Ghislain Adnet <gadnet@aqueos.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Suggestions for building new 44TB Raid5 array
Date: Mon, 20 Jun 2022 08:01:32 -0700	[thread overview]
Message-ID: <20220620150132.GM1664812@merlins.org> (raw)
In-Reply-To: <5e1733e6-471e-e7cb-9588-3280e659bfc2@aqueos.com>

>  I have a stupid question to ask : Why use btrfs here ? Is not mdamd+xfs good enough ?
 
I use btrfs for historical snapshots and btrfs send/receive remote
backups.

>  If you want snapshot why not use ZFS then ? i try to use btrfs myself and meet a lot of issues with it that i did not had with mdadm+ext4. Perhaps btrfs is not suited to that use (here raid5) ?

ZFS is not GPL compatible and out of tree.

>  ZFS has crypt, raid5 like array and snapshot and LARC cache allready so no need to add 4 layer on it. It seems a solution for you.

It has a few of its own issues, but yes, if it were actually GPL
compatible and in the linux kernel source tree, I'd consider it.

It's also owned by a company (Oracle) that has tried to sue others for
billions of dollars over software patents, or even an algorithm, i.e.
not a company I'm willing to trust by any means.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

  parent reply	other threads:[~2022-06-20 15:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  4:51 Suggestions for building new 44TB Raid5 array Marc MERLIN
2022-06-11  9:30 ` Roman Mamedov
     [not found]   ` <CAK-xaQYc1PufsvksqP77HMe4ZVTkWuRDn2C3P-iMTQzrbQPLGQ@mail.gmail.com>
2022-06-11 14:52     ` Marc MERLIN
2022-06-11 17:54       ` Roman Mamedov
2022-06-12 17:31         ` Marc MERLIN
2022-06-12 21:21       ` Roman Mamedov
2022-06-13 17:46         ` Marc MERLIN
2022-06-13 18:06           ` Roman Mamedov
2022-06-14  4:51             ` Marc MERLIN
2022-06-13 18:10           ` Zygo Blaxell
2022-06-13 18:13         ` Marc MERLIN
2022-06-13 18:29           ` Roman Mamedov
2022-06-13 20:08           ` Zygo Blaxell
2022-06-14  6:36             ` Torbjörn Jansson
2022-06-20 20:37       ` Andrea Gelmini
2022-06-21  5:26         ` Zygo Blaxell
2022-07-06  9:09           ` Andrea Gelmini
2022-06-11 23:44 ` Zygo Blaxell
2022-06-14 11:03 ` ronnie sahlberg
     [not found] ` <5e1733e6-471e-e7cb-9588-3280e659bfc2@aqueos.com>
2022-06-20 15:01   ` Marc MERLIN [this message]
2022-06-20 15:52     ` Ghislain Adnet
2022-06-20 16:27       ` Marc MERLIN
2022-06-20 17:02     ` Andrei Borzenkov
2022-06-20 17:26       ` Marc MERLIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220620150132.GM1664812@merlins.org \
    --to=marc@merlins.org \
    --cc=gadnet@aqueos.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.