linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
	linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2] fstests: generic: Check if a bull fallocate will change extent number
Date: Tue, 29 Sep 2015 18:46:23 +0800	[thread overview]
Message-ID: <560A6BFF.2020508@gmx.com> (raw)
In-Reply-To: <20150929103338.GI30949@dhcp-13-216.nay.redhat.com>



在 2015年09月29日 18:33, Eryu Guan 写道:
> On Tue, Sep 29, 2015 at 06:16:11PM +0800, Qu Wenruo wrote:
>>
> <snip>
>>>> +
>>>> +if [ "x$orig_extent_nr" != "x$new_extent_nr" ]; then
>>>> +	echo "number of extents mis-match after bull fallocate"
>>>
>>> print out the $orig_extent_nr and $new_extent_nr in this failure case? I
>>> think it's useful to see the difference just from the output diff, don't
>>> have to check the full file.
>>
>> The problem is, we can't ensure orig/new_extent_nr always be a constant
>> value(1 for btrfs case).
>
> Sorry, I might be unclear, I mean print the extent number in the error
> path, e.g.
>
> echo "number of extents mis-match after null fallocate"
> echo "old: $orig_extent_nr, new: $new_extent_nr"
>
> not matching the number with golden output.
>
> Thanks,
> Eryu

That sounds pretty nice.
Will change it in next version.

Thanks,
Qu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2015-09-29 10:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  9:34 [PATCH v2] fstests: generic: Check if a bull fallocate will change extent number Qu Wenruo
2015-09-29  9:55 ` Eryu Guan
2015-09-29 10:16   ` Qu Wenruo
2015-09-29 10:33     ` Eryu Guan
2015-09-29 10:46       ` Qu Wenruo [this message]
2015-09-29 10:00 ` Hugo Mills
2015-09-29 10:13   ` Qu Wenruo
2015-09-29 10:24     ` Filipe Manana
2015-09-29 10:48       ` Qu Wenruo
2015-09-30  6:42         ` Duncan
2015-09-29 10:24     ` Hugo Mills
2015-09-29 21:51 ` Dave Chinner
2015-09-30  1:05   ` Qu Wenruo
2015-09-30  1:45     ` Tsutomu Itoh
2015-09-30  1:49       ` Qu Wenruo
2015-09-30  4:20     ` Dave Chinner
2015-09-30  5:48       ` Qu Wenruo
2015-10-02  8:35   ` Qu Wenruo
2015-10-06  1:31     ` Dave Chinner

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=560A6BFF.2020508@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).