From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Suggestions for backup scheme?
Date: Wed, 31 Jan 2024 12:56:47 -0500 [thread overview]
Message-ID: <CAGfcS_m6s5BD5KVEzwFaYXQyXu5faXbWBAkcp=6n5rhcvm2tNg@mail.gmail.com> (raw)
In-Reply-To: <e3da6fc9-0688-462a-bb45-54abb5f91cc9@sys-concept.com>
On Wed, Jan 31, 2024 at 12:40 PM Thelma <thelma@sys-concept.com> wrote:
>
> If zfs file system is superior to ext4 and it seems to it is.
> Why hasn't it been adopted more widely in Linux?
>
The main barrier is that its license isn't GPL-compatible. It is
FOSS, but the license was basically designed to keep it from being
incorporated into the mainline kernel.
The odd thing is that right now Oracle controls both ZFS and btrfs,
with the latter doing mostly the same thing and being GPL-compatible,
but it hasn't tended to be as stable. So we're in a really long
transitional period to btrfs becoming as reliable.
ZFS also cannot be shrunk as easily. I think that is something that
has been improved more recently, but I'm not certain of the state of
it. Also, bootloaders like grub aren't 100% compatible with all of
its later features, and it isn't even clear in the docs which ones are
and aren't supported. So it doesn't hurt to keep /boot off of zfs.
I'm sure ext4 also performs better. It has to be faster to just
overwrite a block in place than to remap the extents around the
change, even if the latter is safer. I'd expect zfs to outperform
ext4 with full data journaling though, which would have a comparable
level of safety, assuming it isn't on RAID. I don't think there are
any RAID implementations that do full write journaling to protect
against the write hole problem, but those would obviously underperform
zfs as well.
--
Rich
next prev parent reply other threads:[~2024-01-31 17:57 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 18:15 [gentoo-user] Suggestions for backup scheme? Grant Edwards
2024-01-30 18:47 ` Thelma
2024-01-30 19:29 ` [gentoo-user] " Grant Edwards
2024-01-30 18:54 ` [gentoo-user] " Michael
2024-01-30 19:32 ` [gentoo-user] " Grant Edwards
2024-01-30 19:19 ` [gentoo-user] " Rich Freeman
2024-01-30 19:43 ` [gentoo-user] " Grant Edwards
2024-01-30 20:08 ` [gentoo-user] " Wol
2024-01-30 20:15 ` Rich Freeman
2024-01-30 20:38 ` [gentoo-user] " Grant Edwards
2024-01-31 8:14 ` gentoo-user
2024-01-31 11:45 ` John Covici
2024-01-31 13:01 ` Rich Freeman
2024-01-31 15:50 ` Grant Edwards
2024-01-31 17:40 ` Thelma
2024-01-31 17:56 ` Rich Freeman [this message]
2024-01-31 18:42 ` Wols Lists
2024-01-31 21:30 ` Rich Freeman
2024-02-01 10:16 ` Michael
2024-02-05 12:55 ` J. Roeleveld
2024-02-05 13:35 ` Rich Freeman
2024-02-06 13:12 ` J. Roeleveld
2024-02-06 20:27 ` Wols Lists
2024-02-07 11:11 ` J. Roeleveld
2024-02-07 21:59 ` Wols Lists
2024-02-08 6:32 ` J. Roeleveld
2024-02-08 17:36 ` Wols Lists
2024-02-09 12:53 ` J. Roeleveld
2024-02-06 15:38 ` Grant Edwards
2024-02-06 16:13 ` J. Roeleveld
2024-02-06 17:22 ` Grant Edwards
2024-02-07 11:21 ` J. Roeleveld
2024-01-31 18:00 ` Grant Edwards
2024-02-02 23:39 ` Grant Edwards
2024-02-02 23:58 ` Mark Knecht
2024-02-03 16:02 ` Grant Edwards
2024-02-03 17:05 ` Wol
2024-02-04 6:24 ` Grant Edwards
2024-02-04 9:59 ` Wols Lists
2024-02-04 15:48 ` Grant Edwards
2024-02-05 8:28 ` Wols Lists
2024-02-06 15:35 ` Grant Edwards
2024-02-06 16:19 ` J. Roeleveld
2024-02-06 17:29 ` Grant Edwards
2024-02-07 11:04 ` J. Roeleveld
2024-02-06 23:17 ` Wols Lists
2024-02-07 11:07 ` J. Roeleveld
2024-02-07 21:50 ` Wols Lists
2024-02-08 6:38 ` J. Roeleveld
2024-02-08 17:44 ` Wols Lists
2024-02-09 12:57 ` J. Roeleveld
2024-02-09 15:48 ` Wols Lists
2024-02-09 17:11 ` Peter Humphrey
2024-02-06 20:49 ` Wols Lists
2024-02-03 13:02 ` Michael
2024-02-03 16:15 ` Grant Edwards
2024-02-03 17:32 ` Rich Freeman
2024-02-03 18:10 ` Michael
2024-02-05 12:48 ` J. Roeleveld
2024-01-31 15:38 ` Grant Edwards
2024-02-04 10:54 ` [gentoo-user] " Paul Ezvan
2024-02-07 22:36 ` Frank Steinmetzger
2024-02-08 5:26 ` William Kenworthy
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='CAGfcS_m6s5BD5KVEzwFaYXQyXu5faXbWBAkcp=6n5rhcvm2tNg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox