From: Gao Xiang <xiang@kernel.org>
To: Lucas Karpinski <lkarpinski@nvidia.com>
Cc: linux-erofs@lists.ozlabs.org, jcalmels@nvidia.com
Subject: Re: [PATCH v2 4/5] erofs-utils: mfks: add rebuild FULLDATA for combined EROFS images
Date: Tue, 10 Mar 2026 18:24:16 +0800 [thread overview]
Message-ID: <aa_xUG1Z60A10AMY@debian> (raw)
In-Reply-To: <20260309-merge-fs-v2-4-2dd0ef53db4d@nvidia.com>
Hi Lucas,
On Mon, Mar 09, 2026 at 12:38:20PM -0400, Lucas Karpinski wrote:
> This patch introduces experimental support for merging multiple source
> images in mkfs. Each source image becomes a directory directly under root
> and keeps its UUID stored as a device table tag. The raw block data from
> each source is copied using erofs_copy_file_range. We preserve the file
> metadata and layout (FLAT_PLAIN and FLAT_INLINE). Symlink paths are handled
> by reading and copy link targets.
>
> This does not yet support chunk-based files at this time or compressed
> images.
>
> Signed-off-by: Lucas Karpinski <lkarpinski@nvidia.com>
Thanks for your effort, I finally get the time to look into this
new feature.
So you'd like to cleanly rebuild a new filesystem with given sub
filesystems?
I think first, yes, that is what `--clean=data` is used instead.
But I think uniaddr shouldn't be used like this (uniaddr is used to
give a flat mapping for multiple blobs, in addition to the device id +
offset ones, which is mainly used for compressed data multi blob
support), instead, I think we need to find a way to wrap up the data
source into a valid vfile (so that erofs_pread can be called to get the
source data) , and make erofs_mkfs_job_write_file() to write
(un)compressed data from its source instead.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-03-10 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 16:38 [PATCH v2 0/5] erofs-utils: implement the FULLDATA rebuild mode Lucas Karpinski
2026-03-09 16:38 ` [PATCH v2 1/5] erofs-utils: lib: pass uniaddr_offset to erofs_rebuild_load_tree Lucas Karpinski
2026-03-09 16:38 ` [PATCH v2 2/5] erofs-utils: lib: add helper function erofs_uuid_unparse_as_tag Lucas Karpinski
2026-03-09 16:38 ` [PATCH v2 3/5] erofs-utils: lib: preserve primarydevice_blocks if already larger Lucas Karpinski
2026-03-09 16:38 ` [PATCH v2 4/5] erofs-utils: mfks: add rebuild FULLDATA for combined EROFS images Lucas Karpinski
2026-03-10 10:24 ` Gao Xiang [this message]
2026-03-09 16:38 ` [PATCH v2 5/5] erofs-utils: manpages: update to reflect fulldata support Lucas Karpinski
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=aa_xUG1Z60A10AMY@debian \
--to=xiang@kernel.org \
--cc=jcalmels@nvidia.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=lkarpinski@nvidia.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