All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/288: _notrun if xfs_db write doesn't support -d option
Date: Mon, 30 Jul 2018 16:50:29 +0800	[thread overview]
Message-ID: <5B5ED155.4010700@cn.fujitsu.com> (raw)
In-Reply-To: <20180730074202.26450-1-zlang@redhat.com>

Hi Zorro,

On xfsporgs-dev v4.9.0 which has supported -d option, xfs_db command in
xfs/288 still failed
to set the header count of attr to 0. Is this issue casued by
unsupported -d option on v5 XFS?

Thanks,
Xiao Yang

On 2018/07/30 15:42, Zorro Lang wrote:
> Commit b3cf8b72334fd35ef961869506e5a72ab398bc82 help xfs/288 to
> support v5 filesystems testing, but there're still some old
> distributions don't support xfs_db 'write -d' usage. Then this
> case fails on them.
>
> For compatible with older versions, skip this test on v5 xfs
> if xfs_db write command doesn't support -d option.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>  tests/xfs/288 | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/tests/xfs/288 b/tests/xfs/288
> index bccdb6fc..f8e117ed 100755
> --- a/tests/xfs/288
> +++ b/tests/xfs/288
> @@ -40,6 +40,14 @@ _require_attrs
>  _scratch_mkfs_xfs 2>/dev/null | _filter_mkfs 2>$tmp.mkfs >/dev/null
>  . $tmp.mkfs
>  
> +# Require write -d option to write invalid data into V5 filesystem
> +if [ $_fs_has_crcs -eq 1 ]; then
> +	_scratch_xfs_db -x -c "help write" | egrep -q "(-d)"
> +	if [ $? -ne 0 ]; then
> +		_notrun "xfs_db write doesn't support -d option"
> +	fi
> +fi
> +
>  _scratch_mount
>  
>  touch $SCRATCH_MNT/$seq.attrfile




  reply	other threads:[~2018-07-30 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30  7:42 [PATCH] xfs/288: _notrun if xfs_db write doesn't support -d option Zorro Lang
2018-07-30  8:50 ` Xiao Yang [this message]
2018-07-30  9:16   ` Zorro Lang
2018-07-31  1:49     ` Xiao Yang
2018-07-31  3:28       ` Zorro Lang
2018-07-31  3:39         ` Xiao Yang

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=5B5ED155.4010700@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@redhat.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 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.