linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: "Libor Klepáč" <libor.klepac@bcom.cz>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"quwenruo.btrfs@gmx.com" <quwenruo.btrfs@gmx.com>
Subject: Re: Question about metadata size
Date: Mon, 27 Jun 2022 12:12:01 -0600	[thread overview]
Message-ID: <CAJCQCtQ3qrLTbbXx7KiiU=ZH7NFTFsJVZA0fbKf+EHyCDkJ3Tg@mail.gmail.com> (raw)
In-Reply-To: <f9b7e2fea36afefaec844c385d34b280f766b10b.camel@bcom.cz>

On Mon, Jun 27, 2022 at 4:23 AM Libor Klepáč <libor.klepac@bcom.cz> wrote:

> Yes, we use zstd compression - filesystem is mounted with compress-
> force=zstd:9

compress-force means even uncompressed extents are 512KiB max, so this
could be the source of the problem

If you use just compress, then uncompressed extents can be 128MiB max.

So it's a set of tradeoffs depending on how compressible the files are.



-- 
Chris Murphy

  parent reply	other threads:[~2022-06-27 18:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  9:02 Question about metadata size Libor Klepáč
2022-06-27 10:10 ` Qu Wenruo
2022-06-27 10:23   ` Libor Klepáč
2022-06-27 10:54     ` Qu Wenruo
2022-06-27 12:17       ` Libor Klepáč
2022-06-27 12:39         ` Qu Wenruo
2022-06-27 14:34           ` Libor Klepáč
2022-06-27 14:47           ` Joshua Villwock
2022-06-27 15:13             ` Libor Klepáč
     [not found]             ` <cc28f1516a8fe92007994d1a3fcee93f@mailmag.net>
2022-06-27 15:29               ` Libor Klepáč
2022-06-28 14:18               ` Libor Klepáč
2022-06-27 18:12     ` Chris Murphy [this message]
2022-06-27 22:16       ` remi

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='CAJCQCtQ3qrLTbbXx7KiiU=ZH7NFTFsJVZA0fbKf+EHyCDkJ3Tg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=libor.klepac@bcom.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).