linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Trond Myklebust <trondmy@hammerspace.com>,
	Anna Schumaker <schumakeranna@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: generic/446 failure
Date: Thu, 28 Nov 2019 21:05:38 -0500	[thread overview]
Message-ID: <20191129020538.GA18060@fieldses.org> (raw)

I'm seeing a failure like:

generic/446 32s ... - output mismatch (see /root/xfstests-dev/results//generic/446.out.bad)
    --- tests/generic/446.out	2019-09-18 17:28:00.826721481 -0400
    +++ /root/xfstests-dev/results//generic/446.out.bad	2019-11-28 18:56:36.583719464 -0500
    @@ -1,2 +1,7 @@
     QA output created by 446
    +fallocate: Resource temporarily unavailable
    +fallocate: Resource temporarily unavailable
    +fallocate: Resource temporarily unavailable
    +fallocate: Resource temporarily unavailable
    +fallocate: Resource temporarily unavailable
     Silence is golden
    ...

A bisect pins it on:

	0e0cb35b417f NFSv4: Handle NFS4ERR_OLD_STATEID in CLOSE/OPEN_DOWNGRADE

Have you seen this before?

I took a quick look at a network trace to see if there were
ALLOCATE or DEALLOCATE failures, but there weren't.  The problem doesn't
reproduce when the test is run under strace.  That's all I've tried.

--b.

                 reply	other threads:[~2019-11-29  2:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191129020538.GA18060@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=schumakeranna@gmail.com \
    --cc=trondmy@hammerspace.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).