Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Inline data is compressed unconditinally even when results in increased size
Date: Mon, 14 Sep 2026 23:24:42 +0500	[thread overview]
Message-ID: <ea2a1fbd-a505-4da9-a4f3-51721c914d5b@gmail.com> (raw)
In-Reply-To: <CAL3q7H5dn+NFK+At8+C76r=u==AC_ZivnrvyezwOoWLfjjq9PQ@mail.gmail.com>

> It's a recent regression, independent of the compression algorithm used.
Good that I remember it right, I wasn't sure.
By the way, the actually worst case scenario when it's just 1 byte.

Processed 1 file, 0 regular extents (0 refs), 1 inline.
Type       Perc     Disk Usage   Uncompressed Referenced
TOTAL      1900%      19B           1B           1B
zstd       1900%      19B           1B           1B


      reply	other threads:[~2026-09-14 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 15:46 Inline data is compressed unconditinally even when results in increased size Hanabishi
2026-09-14 17:46 ` Filipe Manana
2026-09-14 18:24   ` Hanabishi [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=ea2a1fbd-a505-4da9-a4f3-51721c914d5b@gmail.com \
    --to=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
    --cc=fdmanana@kernel.org \
    --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