From: Dave Chinner <david@fromorbit.com>
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: xfs@oss.sgi.com
Subject: Re: [Question]: xfstests test generic/233 failure
Date: Wed, 29 Oct 2014 21:36:36 +1100 [thread overview]
Message-ID: <20141029103636.GJ16186@dastard> (raw)
In-Reply-To: <1414575977.17402.3.camel@G08JYZSD130126.localdomain>
On Wed, Oct 29, 2014 at 05:46:17PM +0800, Zeng Linggang wrote:
> Hello,
>
> When I take XFS filesystem as test target, the case generic/233 often
> fails in my test machines (RHEL7.0GA: 3.10.0-123) with output like this:
> generic/233 [failed, exit status 1] - output mismatch (see
> /var/lib/xfstests/results//generic/233.out.bad)
> --- tests/generic/233.out 2014-10-22 14:17:06.239461640 +0800
> +++ results/generic/233.out.bad 2014-10-23 14:39:48.210480319 +0800
> @@ -4,4 +4,7 @@
> seed = S
> Comparing user usage
> -Comparing group usage
> +4c4
> +< #1001 -- 31348 32000 32000 772 1000 1000
> +---
> +> #1001 -- 31144 32000 32000 772 1000 1000
> ...
> generic/231 and generic/270 also have the similar quota accounting mismatch.
fsstress can result in different file and directory layouts, hence
result in different amounts of metadata in the filesystem. Metadata
is also accounted to quotas (e.g. to the user who owns the
directory) and so even if data usage is identical the metadata can
still vary.
I see these test give small variations quite frequently, but they
are are usually only quite small (a handful of blocks) so I've never
really worried about it too much.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-29 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 9:46 [Question]: xfstests test generic/233 failure Zeng Linggang
2014-10-29 10:36 ` Dave Chinner [this message]
2014-10-30 1:37 ` Zeng Linggang
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=20141029103636.GJ16186@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=zenglg.jy@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