From: Martin Steigerwald <martin@lichtvoll.de>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: Read before you deploy btrfs + zstd
Date: Tue, 14 Nov 2017 08:34:37 +0100 [thread overview]
Message-ID: <3013353.6rxLtS64S0@merkaba> (raw)
In-Reply-To: <20171113225046.GD28899@suse.cz>
Hello David.
David Sterba - 13.11.17, 23:50:
> while 4.14 is still fresh, let me address some concerns I've seen on linux
> forums already.
>
> The newly added ZSTD support is a feature that has broader impact than
> just the runtime compression. The btrfs-progs understand filesystem with
> ZSTD since 4.13. The remaining key part is the bootloader.
>
> Up to now, there are no bootloaders supporting ZSTD. This could lead to an
> unmountable filesystem if the critical files under /boot get accidentally
> or intentionally compressed by ZSTD.
But otherwise ZSTD is safe to use? Are you aware of any other issues?
I consider switching from LZO to ZSTD on this ThinkPad T520 with Sandybridge.
Thank you,
--
Martin
next prev parent reply other threads:[~2017-11-14 7:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 22:50 Read before you deploy btrfs + zstd David Sterba
2017-11-14 7:34 ` Martin Steigerwald [this message]
2017-11-14 9:45 ` Paul Jones
2017-11-14 12:38 ` Austin S. Hemmelgarn
2017-11-15 20:23 ` Duncan
2017-11-16 14:31 ` Dmitrii Tcvetkov
2017-11-14 18:49 ` David Sterba
2017-11-14 19:43 ` Martin Steigerwald
2017-11-14 18:53 ` David Sterba
2017-11-15 14:39 ` David Sterba
2017-11-15 16:22 ` Martin Steigerwald
2017-11-15 18:16 ` Imran Geriskovan
2017-11-15 20:06 ` Duncan
2017-11-15 20:09 ` Nick Terrell
2017-11-21 16:22 ` David Sterba
2017-11-28 21:31 ` Nick Terrell
2017-11-28 23:49 ` David Sterba
2017-11-29 0:44 ` Nick Terrell
2017-12-05 15:54 ` David Sterba
2017-12-05 20:36 ` Nick Terrell
2017-11-29 13:24 ` Austin S. Hemmelgarn
2017-11-29 19:29 ` Andrei Borzenkov
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=3013353.6rxLtS64S0@merkaba \
--to=martin@lichtvoll.de \
--cc=dsterba@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).