public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: zenghongling <zenghongling@kylinos.cn>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] mkfs: relax size check
Date: Tue, 29 Nov 2022 11:24:34 +0100	[thread overview]
Message-ID: <Y4Xd4jd/X5zsmoqH@pevik> (raw)
In-Reply-To: <1669691831-23456-1-git-send-email-zenghongling@kylinos.cn>

Hi zenghongling,

> Number of total data blocks in filesystem reported by statfs
> may be less than current formula of 90%. For example ext4 will
> subtract "s_first_data_block plus internal journal blocks".

> With recent change to e2fsprogs, overhead calculated in user-space increased
Do you know in which version it got changed?
Maybe it'd be worth to mention that to ext4 maintainers,
just to be sure it's not a regression.

> slightly and LTP test started failing: tytso/e2fsprogs
A bit cryptic description :(. You mean probably https://github.com/tytso/e2fsprogs
which is also on
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/

Kind regards,
Petr

> mkfs01 1 TPASS: 'mkfs -t ext4  /dev/loop0 ' passed.
> mkfs01 2 TFAIL: 'mkfs -t ext4  /dev/loop0 16000' failed, not expected.

> Since there's no strict rule how much the overhead will be,
> as rule of thumb relax the condition to 70%.

> Signed-off-by: zenghongling <zenghongling@kylinos.cn>
> ---
>  testcases/commands/mkfs/mkfs01.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

> diff --git a/testcases/commands/mkfs/mkfs01.sh b/testcases/commands/mkfs/mkfs01.sh
> index 263aa47..a964774 100755
> --- a/testcases/commands/mkfs/mkfs01.sh
> +++ b/testcases/commands/mkfs/mkfs01.sh
> @@ -66,11 +66,11 @@ mkfs_verify_size()
>  	# 1k-block size should be devided by this argument for ntfs verification.
>  	if [ "$1" = "ntfs" ]; then
>  		local rate=1024/512
> -		if [ $blocknum -lt "$(($2/$rate*8/10))" ]; then
> +		if [ $blocknum -lt "$(($2/$rate*7/10))" ]; then
>  			return 1
>  		fi
>  	else
> -		if [ $blocknum -lt "$(($2*8/10))" ]; then
> +		if [ $blocknum -lt "$(($2*7/10))" ]; then
>  			return 1
>  		fi
>  	fi

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-11-29 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  3:17 [LTP] [PATCH] mkfs: relax size check zenghongling
2022-11-29 10:24 ` Petr Vorel [this message]
2022-11-30  8:06   ` Petr Vorel
2022-12-12 15:03     ` Richard Palethorpe
  -- strict thread matches above, loose matches on Subject: below --
2021-04-23 11:16 Jan Stancek
2021-04-23 15:06 ` Petr Vorel
2021-04-23 15:28   ` Petr Vorel
2021-04-26 13:11 ` Li Wang
2021-04-26 19:28   ` Petr Vorel

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=Y4Xd4jd/X5zsmoqH@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=zenghongling@kylinos.cn \
    /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