All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: xfstests failures with xfs, dax and v4.4-rc3
Date: Wed, 2 Dec 2015 14:02:12 -0600	[thread overview]
Message-ID: <565F4E44.8090200@sandeen.net> (raw)
In-Reply-To: <20151202183438.GA1319@linux.intel.com>



On 12/2/15 12:34 PM, Ross Zwisler wrote:
> I'm hitting a few more test failures in my testing setup with v4.4-rc3, xfs
> and DAX.  My test setup is a pair of 4GiB PMEM partitions in a KVM virtual
> machine.  Here are the failures:

...

> generic/274 7s ... [failed, exit status 1] - output mismatch (see /root/xfstests/results//generic/274.out.bad)
>     --- tests/generic/274.out	2015-10-02 10:19:36.808795907 -0600
>     +++ /root/xfstests/results//generic/274.out.bad	2015-12-02 11:22:37.656868990 -0700
>     @@ -2,4 +2,5 @@
>      ------------------------------
>      preallocation test
>      ------------------------------
>     -done
>     +failed to write to test file
>     +(see /root/xfstests/results//generic/274.full for details)
>     ...
>     (Run 'diff -u tests/generic/274.out /root/xfstests/results//generic/274.out.bad'  to see the entire diff)

I looked at this one a bit last night, and talked to Dave about it; its' different
handling with DAX w.r.t. preallocation; we go down a path which actually tries to
re-reserve the disk blocks it'll be writing to, even though they're already allocated.

If the disk isn't full, I guess it doesn't matter, but this test explicitly tests ENOSPC.

Working on better understanding this path to see if I can fix it (unless Dave beats me
to it ...)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-12-02 20:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 18:34 xfstests failures with xfs, dax and v4.4-rc3 Ross Zwisler
2015-12-02 18:34 ` Ross Zwisler
2015-12-02 20:02 ` Eric Sandeen [this message]
2015-12-02 20:10 ` Dan Williams
2015-12-02 20:10   ` Dan Williams
2015-12-02 20:29 ` Dave Chinner
2015-12-02 20:29   ` Dave Chinner
2015-12-02 20:45   ` Dave Chinner
2015-12-02 20:45     ` Dave Chinner
2015-12-02 21:39     ` Ross Zwisler
2015-12-02 21:39       ` Ross Zwisler
2015-12-10 16:54       ` Ross Zwisler
2015-12-10 16:54         ` Ross Zwisler
2015-12-10 22:33         ` Dave Chinner
2015-12-10 22:33           ` Dave Chinner
2015-12-11  4:26           ` Ross Zwisler
2015-12-11  4:26             ` Ross Zwisler
2015-12-14  0:20             ` Dave Chinner
2015-12-14  0:20               ` 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=565F4E44.8090200@sandeen.net \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.