All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3 4/4] xfs/144: remove testing root dir inode in AG 1
Date: Tue, 30 Aug 2022 15:49:36 +0800	[thread overview]
Message-ID: <20220830074936.eprwzg4auxtlhsom@zlang-mailbox> (raw)
In-Reply-To: <20220830044433.1719246-5-jencce.kernel@gmail.com>

On Tue, Aug 30, 2022 at 12:44:33PM +0800, Murphy Zhou wrote:
> Since this xfsprogs commit
>   1b580a773 mkfs: don't let internal logs bump the root dir inode chunk to AG 1
> this operation is not allowed.
> 
> Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
> ---
>  tests/xfs/144 | 10 +---------
>  1 file changed, 1 insertion(+), 9 deletions(-)
> 
> diff --git a/tests/xfs/144 b/tests/xfs/144
> index 706aff61..3f80d0ee 100755
> --- a/tests/xfs/144
> +++ b/tests/xfs/144
> @@ -17,9 +17,6 @@ _begin_fstest auto mkfs
>  _supported_fs xfs
>  _require_test
>  
> -# The last testcase creates a (sparse) fs image with a 2GB log, so we need
> -# 3GB to avoid failing the mkfs due to ENOSPC.
> -_require_fs_space $TEST_DIR $((3 * 1048576))
>  echo Silence is golden
>  
>  testfile=$TEST_DIR/a
> @@ -36,7 +33,7 @@ test_format() {
>  }
>  
>  # First we try various small filesystems and stripe sizes.
> -for M in `seq 298 302` `seq 490 520`; do
> +for M in `seq 1024 1030` ; do

Can `seq 1024 1030` replace `seq 298 302` `seq 490 520`? I don't know how
Darrick choose these numbers, better to ask the original authoer of this
case. Others looks reasonable for me.

Thanks,
Zorro

>  	for S in `seq 32 4 64`; do
>  		test_format "M=$M S=$S" -dsu=${S}k,sw=1,size=${M}m -N
>  	done
> @@ -45,11 +42,6 @@ done
>  # log end rounded beyond EOAG due to stripe unit
>  test_format "log end beyond eoag" -d agcount=3200,size=6366g -d su=256k,sw=4 -N
>  
> -# Log so large it pushes the root dir into AG 1.  We can't use -N for the mkfs
> -# because this check only occurs after the root directory has been allocated,
> -# which mkfs -N doesn't do.
> -test_format "log pushes rootdir into AG 1" -d agcount=3200,size=6366g -lagnum=0
> -
>  # success, all done
>  status=0
>  exit
> -- 
> 2.31.1
> 


  reply	other threads:[~2022-08-30  7:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  4:44 [PATCH v3 0/4] tweaks for denying tiny xfs Murphy Zhou
2022-08-30  4:44 ` [PATCH v3 1/4] tests: increase fs size for mkfs Murphy Zhou
2022-08-30  7:36   ` Zorro Lang
2022-08-30 14:46     ` Darrick J. Wong
2022-08-30 19:07       ` Zorro Lang
2022-08-31  0:18         ` Murphy Zhou
2022-08-31  1:53           ` Murphy Zhou
2022-08-31  5:04             ` Zorro Lang
2022-08-31  9:34               ` Murphy Zhou
2022-08-30  4:44 ` [PATCH v3 2/4] tests: increase xfs log size Murphy Zhou
2022-08-30  4:44 ` [PATCH v3 3/4] tests/xfs: remove single-AG options Murphy Zhou
2022-08-30 13:42   ` Zorro Lang
2022-08-31  0:02     ` Murphy Zhou
2022-08-30 15:05   ` Darrick J. Wong
2022-08-31  0:10     ` Murphy Zhou
2022-08-30  4:44 ` [PATCH v3 4/4] xfs/144: remove testing root dir inode in AG 1 Murphy Zhou
2022-08-30  7:49   ` Zorro Lang [this message]
2022-08-30 14:59     ` Darrick J. Wong
2022-08-30 23:45       ` Murphy Zhou
2022-08-30 23:42     ` Murphy Zhou

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=20220830074936.eprwzg4auxtlhsom@zlang-mailbox \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.