[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151201235158.GF19199@dastard>
Date: Wed, 2 Dec 2015 10:51:58 +1100
From: Dave Chinner <david@...morbit.com>
To: Ross Zwisler <ross.zwisler@...ux.intel.com>, xfs@....sgi.com,
Brian Foster <bfoster@...hat.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: xfstest failure with xfs, dax and v4.4-rc3
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@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists