public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ferry Toth <fntoth@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>
Subject: Re: Errors on newly created file system
Date: Sat, 26 Apr 2025 22:42:20 +0200	[thread overview]
Message-ID: <4012f82a-191b-4023-9079-0dde92eff242@gmail.com> (raw)
In-Reply-To: <b2ac7b22-ab50-4eb4-a90a-0d110407ba36@gmx.com>

Op 24-04-2025 om 01:24 schreef Qu Wenruo:
> 在 2025/4/24 01:36, Ferry Toth 写道:
>> Op woensdag 23 april 2025 00:00:36 CEST schreef Qu Wenruo:

>> While here, am I right that we can not generate the rootfs with 
>> compression on?
>>
>>
>> Reason I ask is, Yocto of course builds the rootfs and than has 
>> mkfs.btrfs create the image. But it runs as unprivileged user, so can 
>> not do mount.
>>
>> And then can not do defrag.
> 
> We have this feature recently thanks to Mark!
> 
> In the latest release v6.13, there is a new option "--compress" added to 
> mkfs.btrfs, which must be used with "--rootdir".

I built 6.14 while configuring with --enable-lzo

Configure says:
	zstd support:       no
	lzo support:        yes

Finally running mkfs.btrfs with --compress lzo

I get:
-EXPERIMENTAL -INJECT -STATIC -LZO -ZSTD -UDEV +FSVERITY -ZONED 
CRYPTO=builtin

And
ERROR: lzo support not compiled in

Strangely: when I run with --compress zlib and I check the resulting 
image with btrfs-compsize it says:

Processed 8969984 files, 2574779 regular extents (6008702 refs), 5007593 
inline.
Type       Perc     Disk Usage   Uncompressed Referenced
TOTAL       91%      532G         582G         820G
none       100%      489G         489G         575G
zlib        38%      350M         902M         926M
lzo         46%       42G          92G         243G
prealloc   100%       99M          99M         678M

Seems like it tries lzo anyway and is mixed up about support not built in.

      parent reply	other threads:[~2025-04-26 20:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-20 21:45 Errors on newly created file system Ferry Toth
2025-04-20 22:00 ` Qu Wenruo
2025-04-22 21:32   ` Ferry Toth
2025-04-22 22:00     ` Qu Wenruo
2025-04-23 16:06       ` Ferry Toth
2025-04-23 23:24         ` Qu Wenruo
2025-04-24 11:31           ` Ferry Toth
2025-04-24 20:11             ` Ferry Toth
2025-04-24 20:49               ` Qu Wenruo
2025-04-24 21:16                 ` Ferry Toth
2025-04-26 21:01                   ` Ferry Toth
2025-04-26 20:42           ` Ferry Toth [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=4012f82a-191b-4023-9079-0dde92eff242@gmail.com \
    --to=fntoth@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.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