Linux NFS development
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: generic/650 makes v6.0-rc client unusable
Date: Sun, 4 Sep 2022 08:48:42 -0400	[thread overview]
Message-ID: <YxSeqjkKvz+Y2AcP@mit.edu> (raw)
In-Reply-To: <3E21DFEA-8DF7-484B-8122-D578BFF7F9E0@oracle.com>

On Sat, Sep 03, 2022 at 06:43:29PM +0000, Chuck Lever III wrote:
> While investigating some of the other issues that have been
> reported lately, I've found that my v6.0-rc3 NFS/TCP client
> goes off the rails often (but not always) during generic/650.
> 
> This is the test that runs a workload while offlining and
> onlining CPUs. My test client has 12 physical cores.
> 
> The test appears to start normally, but then after a bit
> the NFS server workload drops to zero and the NFS mount
> disappears. I can't run programs (sudo, for example) on
> the client. Can't log in, even on the console. The console
> has a constant stream of "can't rotate log: Input/Output
> error" type messages.

I've noticed problems with generic/650 for quite a while, but only
when running tests on GCE (but not KVM).  I noted this not when
running xfstests on ext4; IIRC, it was was causing the VM to reboot
when testing any file system.

							- Ted

commit 6e7867469bd3b135125a76e633e0bb50045ccb3c
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Fri Oct 22 23:24:31 2021 -0400

    test-appliance: allow tests to be excluded based on the appliance flavor
    
    The generic/650 test causes an instant reboot on GCE, so add
    infrastructure to exclude a test based on the test appliance flavor
    (i.e., android, gce, or kvm).
    
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

  parent reply	other threads:[~2022-09-04 12:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03 18:43 generic/650 makes v6.0-rc client unusable Chuck Lever III
2022-09-04  8:49 ` David Wysochanski
2022-09-04 12:48 ` Theodore Ts'o [this message]
2022-09-04 13:15 ` Zorro Lang
2022-09-04 16:02   ` Chuck Lever III
2022-09-06 15:50     ` Chuck Lever III
2022-11-09  4:19   ` Shinichiro Kawasaki
2022-11-09 10:36     ` Filipe Manana
2022-11-09 18:06       ` Darrick J. Wong
2022-11-10  8:49         ` Shinichiro Kawasaki
2022-11-10 15:21         ` Theodore Ts'o
2022-11-10  8:46       ` Shinichiro Kawasaki

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=YxSeqjkKvz+Y2AcP@mit.edu \
    --to=tytso@mit.edu \
    --cc=chuck.lever@oracle.com \
    --cc=fstests@vger.kernel.org \
    --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