From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@suse.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: fix test btrfs/017 (qgroup shared extent accounting test)
Date: Thu, 15 Jan 2015 12:28:00 +0100 [thread overview]
Message-ID: <20150115112800.GB3685@twin.jikos.cz> (raw)
In-Reply-To: <1421277703-32154-1-git-send-email-fdmanana@suse.com>
On Wed, Jan 14, 2015 at 11:21:43PM +0000, Filipe Manana wrote:
> Currently this test fails on 2 situations:
>
> 1) The scratch device supports trim/discard. In this case any modern
> version of mkfs.btrfs outputs a message (to stderr) informing that
> a trim is performed, which the golden output doesn't expect:
>
> btrfs/017 - output mismatch (see /git/xfstests/results//btrfs/017.out.bad)
> --- tests/btrfs/017.out 2015-01-06 11:14:22.730143144 +0000
> +++ /git/xfstests/results//btrfs/017.out.bad 2015-01-14 22:33:01.582195719 +0000
> @@ -1,4 +1,5 @@
> QA output created by 017
> +Performing full device TRIM (100.00GiB) ...
> wrote 8192/8192 bytes at offset 0
> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> 4096 4096
> ...
> (Run 'diff -u tests/btrfs/017.out /git/xfstests/results//btrfs/017.out.bad' to see the entire diff)
>
> So like others tests do, just redirect mkfs' standard error.
>
> 2) On platforms with a page size greater than 4Kb. At the moment btrfs
> doesn't support a node/leaf size smaller than the page size, but it
> supports a larger one. So use the max supported node size (64Kb) so
> that the test runs on any platform currently supported by Linux.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
prev parent reply other threads:[~2015-01-15 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:21 [PATCH] fstests: fix test btrfs/017 (qgroup shared extent accounting test) Filipe Manana
2015-01-15 11:28 ` David Sterba [this message]
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=20150115112800.GB3685@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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