linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
	xfs@oss.sgi.com, Brian Foster <bfoster@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: xfstest failure with xfs, dax and v4.4-rc3
Date: Wed, 2 Dec 2015 10:51:58 +1100	[thread overview]
Message-ID: <20151201235158.GF19199@dastard> (raw)
In-Reply-To: <20151201224346.GA15684@linux.intel.com>

On Tue, Dec 01, 2015 at 03:43:46PM -0700, Ross Zwisler wrote:
> I'm seeing a new intermittent xfstests failure with v4.4-rc3 using XFS and
> DAX.  The test that is failing is generic/083, and it fails about 50% of the
> time in my setup.  Here's the output:
> 
> FSTYP         -- xfs (debug)
> PLATFORM      -- Linux/x86_64 lorwyn 4.4.0-rc3
> MKFS_OPTIONS  -- -f -bsize=4096 /dev/pmem0p2
> MOUNT_OPTIONS -- -o dax -o context=system_u:object_r:nfs_t:s0 /dev/pmem0p2
> /mnt/xfstests_scratch
> 
> generic/083 2s ... 2s
> _check_xfs_filesystem: filesystem on /dev/pmem0p2 is inconsistent (r) (see
> /root/xfstests/results//generic/083.full)
> Ran: generic/083
> Failures: generic/083
> Failed 1 of 1 tests

$ grep 083  tests/xfs/group
083 dangerous_fuzzers
$

Yup, it's expected to fail, and given that it's "dangerous" likely
to hang the filesystem or crash the kernel.

Tests that are expected to pass and act as regression tests are in
the auto group. If a test is not in the auto group, it's usually
because the test is either broken or will not complete due
hanging/crashing. i.e use:

# MOUNT_OPTIONS="-o dax" ./check -g auto

For regression testing.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-12-01 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 22:43 xfstest failure with xfs, dax and v4.4-rc3 Ross Zwisler
2015-12-01 23:51 ` Dave Chinner [this message]
2015-12-02 15:12   ` Jeff Moyer
2015-12-03  6:51     ` Dave Chinner
2015-12-03 16:43       ` Ross Zwisler

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=20151201235158.GF19199@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).