From: Imran Geriskovan <imran.geriskovan@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: zstd compression
Date: Wed, 15 Nov 2017 10:51:24 +0200 [thread overview]
Message-ID: <CAK5rZE51onZEE_f2xg4nxPriU9YQq5AARDLs-BTZL2RaGSCTXA@mail.gmail.com> (raw)
Kernel 4.14 now includes btrfs zstd compression support.
My question:
I currently have a fs mounted and used with "compress=lzo"
option. What happens if I change it to "compress=zstd"?
My guess is that existing files will be read and uncompressed via lzo.
And new files will be written with zstd compression. And
everything will run smoothly.
Is this optimistic guess valid? What are possible pitfalls,
if there are any? Any further advices?
Regards,
Imran
next reply other threads:[~2017-11-15 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 8:51 Imran Geriskovan [this message]
2017-11-15 10:09 ` zstd compression Lukas Pirl
2017-11-15 10:35 ` Imran Geriskovan
2017-11-15 12:57 ` Austin S. Hemmelgarn
2017-11-15 21:31 ` Duncan
2017-11-16 12:30 ` Austin S. Hemmelgarn
2017-11-16 12:51 ` Imran Geriskovan
2017-11-16 13:43 ` Duncan
2017-11-16 16:32 ` Austin S. Hemmelgarn
2017-11-16 20:36 ` Timofey Titovets
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=CAK5rZE51onZEE_f2xg4nxPriU9YQq5AARDLs-BTZL2RaGSCTXA@mail.gmail.com \
--to=imran.geriskovan@gmail.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 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).