From: Nikolay Borisov <nborisov@suse.com>
To: Peter Kese <peter.kese@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: compress-force mount option documentation is ambiguous
Date: Tue, 18 Aug 2020 09:34:32 +0300 [thread overview]
Message-ID: <ffa40b36-596d-ce39-fe99-3a194b313718@suse.com> (raw)
In-Reply-To: <e82fe98f-c76d-02df-ee28-d1c77ab91139@suse.com>
On 18.08.20 г. 9:18 ч., Nikolay Borisov wrote:
>
>
> On 17.08.20 г. 23:18 ч., Peter Kese wrote:
>> The `compress-force` mount option which states:
>>
>> "If compress-force is specified, then compression will always be
>> attempted, but the data may end up uncompressed if the compression
>> would make them larger."
>
> So which part is ambiguous - it clearly states that so long as
> compress-force is specified compression is _always_ attempted but it
> might not always be performed because of heuristics present that check if
> compressed size < original size. That heuristics is independent of
> whether compression is enabled or not. I.e it is always performed if
> compression is enabled. In this regard I think the text is clear, how
> would you recommend changing the docs?
Huhz I was wrong, indeed if force compress is enabled then even if the
file is made larger then btrfs will still "compress" it.
>
>>
>> It is unclear whether that means that compress-force will really
>> ALWAYS attempt compression, or it will respect the +c / -c file
>> attributes?
FORCE_COMPRESS disregards +/- c in this case.
>>
>> Which one is it? Can we fix the documentation?
>
>
>
>> Thanks
>>
>
prev parent reply other threads:[~2020-08-18 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 20:18 compress-force mount option documentation is ambiguous Peter Kese
2020-08-18 0:10 ` Andrew Skretvedt
2020-08-18 6:39 ` Nikolay Borisov
2020-08-18 6:18 ` Nikolay Borisov
2020-08-18 6:34 ` Nikolay Borisov [this message]
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=ffa40b36-596d-ce39-fe99-3a194b313718@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=peter.kese@gmail.com \
/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