linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: 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: Thu, 3 Dec 2015 17:51:27 +1100	[thread overview]
Message-ID: <20151203065127.GB26718@dastard> (raw)
In-Reply-To: <x49k2owq3z6.fsf@segfault.boston.devel.redhat.com>

On Wed, Dec 02, 2015 at 10:12:29AM -0500, Jeff Moyer wrote:
> Dave Chinner <david@fromorbit.com> writes:
> 
> > 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
> > $
> 
> That's great, but Ross reported an issues with *generic*/083.  ;-)
> 
> /me hands Dave more coffee.

Ah, some days I need more coffee than others :/

As it is, that test does not fail on my DAX testing on RAM disks.
ISTR it failing up until recently, though. Yeah:

Last login: Tue Nov 17 08:45:55 2015 from 192.168.1.103
$ cd ~/src/xfstests-dev; sudo mkfs.xfs -f /dev/ram0 ; sudo xfs_admin -U generate /dev/ram0 ; sudo MOUNT_OPTIONS="-o dax" ./check -g auto
SECTION       -- xfs
FSTYP         -- xfs (debug)
PLATFORM      -- Linux/x86_64 test4 4.3.0-dgc+
MKFS_OPTIONS  -- -f -bsize=4096 /dev/ram1
MOUNT_OPTIONS -- -o dax /dev/ram1 /mnt/scratch
....
generic/083 2s ... 1s
_check_xfs_filesystem: filesystem on /dev/ram1 is inconsistent (c) (see /home/dave/src/xfstests-dev/results//xfs/generic/083.full)
_check_xfs_filesystem: filesystem on /dev/ram1 is inconsistent (r) (see /home/dave/src/xfstests-dev/results//xfs/generic/083.full)
....

But as I ran earlier today when testing the ENOSPC fix:

PLATFORM      -- Linux/x86_64 test4 4.4.0-rc2-dgc+
MKFS_OPTIONS  -- -f -bsize=4096 /dev/ram1
MOUNT_OPTIONS -- -o dax /dev/ram1 /mnt/scratch
....
generic/083 1s ... 2s
....

So I'm seeing that the current 4.4-rc2 + my local dev tree patches
appear to have fixed whatever was causing generic/083 to fail
here...

What version of xfsprogs are you using, Ross?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-12-03  6:52 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
2015-12-02 15:12   ` Jeff Moyer
2015-12-03  6:51     ` Dave Chinner [this message]
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=20151203065127.GB26718@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=jmoyer@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).