public inbox for linux-erofs@ozlabs.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Lucas Karpinski <lkarpinski@nvidia.com>, linux-erofs@lists.ozlabs.org
Cc: jcalmels@nvidia.com
Subject: Re: [PATCH experimental-tests] erofs-utils: tests: add test for rebuild fulldata
Date: Mon, 20 Apr 2026 16:20:59 +0800	[thread overview]
Message-ID: <3d2e0a50-abc7-4479-9437-d44066d891d5@linux.alibaba.com> (raw)
In-Reply-To: <20260417-b4-fulldata-test-v1-1-234654bdb930@nvidia.com>

Hi Lucas,

On 2026/4/18 04:06, Lucas Karpinski wrote:
> Add a regression test for building a self-contained image out of two other
> erofs images.
> 
> 1. Create img1 & img2 with various file types and sizes.
> 2. Rebuild a new self-contained image of img1 & img2.
> 3. Delete img1 & img2 to prove that this isn't use the blob based rebuild
>     path.
> 4. Mount the new self-contained image and compare the checksum to the
>     original folders.

Thanks for the patch. I wonder if it's possible to:
  1) Use a common dataset as the base layer (see other existing tests);
  2) Mount two overlayfs to get the incremental layers;
     - one to generate some artifacial dirs, files;
     - the other to change/delete some files, or delete dirs, new another
       dirs;
  3) Test typical metadata (whiteout, opaque), and data with:
     a) fsmerged erofs;
     b) overlayfs mount;
     fssum those two mounts.

Thanks,
Gao Xiang


  reply	other threads:[~2026-04-20  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 20:06 [PATCH experimental-tests] erofs-utils: tests: add test for rebuild fulldata Lucas Karpinski
2026-04-20  8:20 ` Gao Xiang [this message]
2026-04-21 17:04 ` [PATCH v2 " 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=3d2e0a50-abc7-4479-9437-d44066d891d5@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --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