FS/XFS testing framework
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Eryu Guan <eguan@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/078: omit -m crc=0 mkfs option if mkfs.xfs has no meta support
Date: Wed, 22 Jul 2015 10:22:56 -0500	[thread overview]
Message-ID: <55AFB550.5020904@sandeen.net> (raw)
In-Reply-To: <1437553336-30408-1-git-send-email-eguan@redhat.com>

On 7/22/15 3:22 AM, Eryu Guan wrote:
> This basically does the same as in commit
> 
> 90a3bfc xfs: be compatible with older mkfs.xfs which has no v5 support
> 
> which left xfs/078 behind.
> 
> Signed-off-by: Eryu Guan <eguan@redhat.com>

This is fine as far as it goes, but I think xfs/045 needs it too:


if ! _scratch_mkfs_xfs -m crc=0 >$tmp.out 2>&1
then
    cat $tmp.out
    echo "!!! failed to mkfs on $SCRATCH_DEV"
    exit
fi

It fails "gracefully" but it doesn't need to, in this case.

In case I'm wrong, for this patch:

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

but xfs/045 might need a look too, either in this patch or a followup.

Thanks,
-Eric

> ---
>  tests/xfs/078 | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/xfs/078 b/tests/xfs/078
> index 32436f7..0d6eb55 100755
> --- a/tests/xfs/078
> +++ b/tests/xfs/078
> @@ -87,7 +87,11 @@ _grow_loop()
>  	echo
>  
>  	echo "*** mkfs loop file (size=$original)"
> -	$MKFS_XFS_PROG -m crc=0 -b size=$bsize -d $dparam \
> +	mkfs_crc_opts="-m crc=0"
> +	if [ -n "$XFS_MKFS_HAS_NO_META_SUPPORT" ]; then
> +		mkfs_crc_opts=""
> +	fi
> +	$MKFS_XFS_PROG $mkfs_crc_opts -b size=$bsize -d $dparam \
>  		| _filter_mkfs 2>/dev/null
>  
>  	echo "*** extend loop file"
> 


  reply	other threads:[~2015-07-22 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22  8:22 [PATCH] xfs/078: omit -m crc=0 mkfs option if mkfs.xfs has no meta support Eryu Guan
2015-07-22 15:22 ` Eric Sandeen [this message]
2015-07-23  3:54   ` Eryu Guan
2015-07-23  3:56     ` Eric Sandeen

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=55AFB550.5020904@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=eguan@redhat.com \
    --cc=fstests@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