linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Olga Kornievskaia <aglo@umich.edu>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: discuss NFS xfstest failures
Date: Tue, 16 Apr 2019 15:35:48 -0400	[thread overview]
Message-ID: <20190416193548.GA6662@fieldses.org> (raw)
In-Reply-To: <CAN-5tyHGLTFmd1t9Bn4VqbLFsnvTMJYd-dBzrn9mP-Tn7g8XVg@mail.gmail.com>

On Thu, Apr 11, 2019 at 01:01:39PM -0400, Olga Kornievskaia wrote:
> Hi folks,
> 
> We have some output at the wiki --
> https://wiki.linux-nfs.org/wiki/index.php/Xfstests -- capturing a data
> point of failures (for 4.16 kernel). However, I see many more failures
> with the current (5.1-rc1). Wiki output should probably be updated
> since xfstest has now 500+ tests. I have done my best to go over the
> failures and provide some summary and comments. I'd like to see if the
> community has any comments. Anybody else would like to share their
> outputs from the xfstests that show other failures?

For what it's worth, I keep a list in testd/data/xfstests-failed with
some minimal comments:

	git://linux-nfs.org/~bfields/testd.git

Current contents appended.  As you can see there's a lot that's known
unsupported features, but also a lot that I just haven't looked into
yet.

--b.

# http://people.redhat.com/bcodding/nfs/2016/10/07/nfs_xfstest_generic/
generic/035
generic/087
generic/294
generic/306
# We don't support all fallocate modes
generic/031
generic/017
generic/062
generic/071
generic/422
generic/469
generic/499
# no fiemap
generic/032
generic/094
generic/225
generic/425
# no xattrs
generic/037
generic/337
generic/377
generic/403
generic/454
# NFSv4+ doesn't support system.posix_acl_access xattr:
generic/053
generic/105
# xfstests used to skip this, not sure why it stopped:
generic/064
# no support for fs freezing
generic/068
generic/491
# needs root?
generic/184
generic/434
# FIBMAP unsupported
generic/519
# ---- need further triage:
generic/033
generic/088 # intermittent ?
generic/089 # intermittent ?
generic/126
generic/277
generic/423
generic/426
generic/465
generic/478
# "record lock is not preserved across execve(2)"
generic/484
# need a larger device?
generic/485
generic/486

  reply	other threads:[~2019-04-16 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 17:01 discuss NFS xfstest failures Olga Kornievskaia
2019-04-16 19:35 ` J. Bruce Fields [this message]
2019-05-15 18:30   ` J. Bruce Fields

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=20190416193548.GA6662@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    /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).