From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Alex Lyakas <alex@zadarastorage.com>, xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfstests updated to 197f773
Date: Mon, 3 Feb 2014 09:35:25 +1100 [thread overview]
Message-ID: <20140202223525.GW2212@dastard> (raw)
In-Reply-To: <52E95EB8.8080003@sandeen.net>
On Wed, Jan 29, 2014 at 02:04:08PM -0600, Eric Sandeen wrote:
> On 1/29/14, 1:55 PM, Alex Lyakas wrote:
> > Hi Dave,
> > are all tests in xfstests (those relevant for XFS) in principle
> > supposed to pass on XFS?
> > I am running these tests on a pristine XFS from kernel 3.8.13
> > (srcversion 9862FA08CF42E06A4151111) and I get:
> >
> > root@vc-13-12-1095-35-dev:/mnt/work/alex/xfstests# ./check tests/generic/013
> > FSTYP -- xfs (non-debug)
> > PLATFORM -- Linux/x86_64 vc-13-12-1095-35-dev 3.8.13-030813-generic
> > MKFS_OPTIONS -- -f -bsize=4096 /dev/vdb
> > MOUNT_OPTIONS -- /dev/vdb /mnt/SCRATCH_DIR
> >
> > generic/013 34s
> > _check_xfs_filesystem: filesystem on /dev/vda is inconsistent (c) (see
> > /mnt/work/alex/xfstests/results//generic/013.full)
>
> uh, so it failed
>
> > Ran: generic/013
> > Passed all 1 tests
>
> but it passed? ;)
It passed the test, but failed the post test filesystem checks.
> The fact that you saw:
>
> > generic/013 34s
>
> and not:
>
> > generic/013 34s ... 33s
> or
> > generic/013 34s ... output mismatch
>
> or similar, makes me think the test did not even start, and /dev/vda was
> corrupted before you even started the test, but I'm not certain.
No, what that means is that there was no results/check.time file
that had previous runtime information in it. i.e. this is the first
time the test was run, or that it has always failed like this in the
past on this machine.
As it is:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
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-02-02 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 2:58 [ANNOUNCE] xfstests updated to 197f773 Dave Chinner
2014-01-29 19:55 ` Alex Lyakas
2014-01-29 20:04 ` Eric Sandeen
2014-02-02 22:35 ` Dave Chinner [this message]
2014-02-04 17:53 ` Alex Lyakas
2014-02-04 22:23 ` 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=20140202223525.GW2212@dastard \
--to=david@fromorbit.com \
--cc=alex@zadarastorage.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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