public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: generic/042: increase filesystem image size
Date: Wed, 9 Jul 2025 14:15:57 +0930	[thread overview]
Message-ID: <1ab3b61e-bbca-42e0-bb97-9bdd5de068f3@gmx.com> (raw)
In-Reply-To: <05033925fe12eccf80c07396edb9acc8e1cb6778.1752035731.git.anand.jain@oracle.com>



在 2025/7/9 14:10, Anand Jain 写道:
> During testing for shutdown, I found that generic/042 sets a size of
> 25M, which is too small for btrfs. Setting it to 128M.
> 
> wrote 26214400/26214400 bytes at offset 0
> 25 MiB, 6400 ops; 0.0468 sec (533.618 MiB/sec and 136606.1900 ops/sec)
> ERROR: '/mnt/scratch/042.img' is too small to make a usable filesystem
> ERROR: minimum size for each btrfs device is 114294784
> 
> Signed-off-by: Anand Jain <anand.jain@oracle.com>

Already submitted:

https://lore.kernel.org/linux-btrfs/20250625232021.69787-1-wqu@suse.com/

Thanks,
Qu

> ---
>   tests/generic/042 | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/generic/042 b/tests/generic/042
> index ced145dde753..6cd2e7a3703a 100755
> --- a/tests/generic/042
> +++ b/tests/generic/042
> @@ -26,7 +26,7 @@ _crashtest()
>   	img=$SCRATCH_MNT/$seq.img
>   	mnt=$SCRATCH_MNT/$seq.mnt
>   	file=$mnt/file
> -	size=$(_small_fs_size_mb 25)M
> +	size=$(_small_fs_size_mb 128)M
>   
>   	# Create an fs on a small, initialized image. The pattern is written to
>   	# the image to detect stale data exposure.


      reply	other threads:[~2025-07-09  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  4:40 [PATCH] fstests: generic/042: increase filesystem image size Anand Jain
2025-07-09  4:45 ` Qu Wenruo [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=1ab3b61e-bbca-42e0-bb97-9bdd5de068f3@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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