From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Ferry Toth <fntoth@gmail.com>,
linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>
Subject: Re: Errors on newly created file system
Date: Thu, 24 Apr 2025 08:54:23 +0930 [thread overview]
Message-ID: <b2ac7b22-ab50-4eb4-a90a-0d110407ba36@gmx.com> (raw)
In-Reply-To: <2366963.X513TT2pbd@ferry-quad>
在 2025/4/24 01:36, Ferry Toth 写道:
> Op woensdag 23 april 2025 00:00:36 CEST schreef Qu Wenruo:
>
[...]
>
> > > Yocto users on Scarthgap (5.0 LTS) with version 6.7.1 may copy the
>
> > > recipe meta/recipes-devtools/btrfs-tools/btrfs-tools_6.13.bb from
>
> > > walnascar or 6.14 from master. If they are building additional tools
>
> > > that use headers from this package like btrfs-compsize these may break.
>
> > >> Thanks,
>
> > >> Qu
>
>
> 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".
And the result is exactly what you expected, mkfs.btrfs will try to
compress the file extents at runtime.
For uncompressible data, it will detect at the beginning and fallback to
uncompressed data instead, exactly like the kernel.
But considering how new this feature this, it will be appreciated if
Yocto guys can do some extra testing to make sure nothing is broken.
(Normally a btrfs check after the mkfs will be good enough)
Thanks,
Qu
>
>
> > >
>
> > >
>
> >
>
> >
>
>
>
next prev parent reply other threads:[~2025-04-23 23:24 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 [this message]
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
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=b2ac7b22-ab50-4eb4-a90a-0d110407ba36@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=fntoth@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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