From: Roman Mamedov <rm@romanrm.net>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: do not allow -o compress-force to override per-inode settings
Date: Mon, 30 Nov 2020 20:17:17 +0500 [thread overview]
Message-ID: <20201130201717.49ec8031@natsu> (raw)
In-Reply-To: <df787c30-8a5e-0256-a4c9-baa3e3556a39@toxicpanda.com>
On Mon, 30 Nov 2020 10:10:42 -0500
Josef Bacik <josef@toxicpanda.com> wrote:
> Right, but if we have compress-force we don't set NOCOMPRESS if the compression
> is bad, so theoretically we shouldn't ever really have that problem?
It is persistent on disk, so remounting or mounting next time with
compress-force would now skip compression for those files which were deemed
having a bad compression ratio at some point in the past.
--
With respect,
Roman
next prev parent reply other threads:[~2020-11-30 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 13:46 [PATCH] btrfs: do not allow -o compress-force to override per-inode settings Josef Bacik
2020-11-30 14:08 ` Roman Mamedov
2020-11-30 14:27 ` Amy Parker
2020-11-30 14:50 ` Josef Bacik
2020-11-30 15:01 ` Roman Mamedov
2020-11-30 15:10 ` Josef Bacik
2020-11-30 15:17 ` Roman Mamedov [this message]
2020-11-30 15:04 ` Hugo Mills
2020-11-30 15:12 ` Josef Bacik
2020-11-30 17:28 ` sys
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=20201130201717.49ec8031@natsu \
--to=rm@romanrm.net \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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.