From: "Theodore Ts'o" <tytso@mit.edu>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Boyang Xue <bxue@redhat.com>,
"Darrick J. Wong" <djwong@kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: [PATCH v1] generic/476: requires 27GB scratch size
Date: Thu, 21 Jul 2022 14:04:15 -0400 [thread overview]
Message-ID: <YtmVH8HNHHxVUyoM@mit.edu> (raw)
In-Reply-To: <6C27EF62-B619-4451-9CBC-B21CEC72F66D@oracle.com>
On Thu, Jul 21, 2022 at 03:14:30PM +0000, Chuck Lever III wrote:
> > - Loopback means there's often no way to know which part of
> > the stack (client or server) is the problem.
>
> And by the way, it's even worse if that single system acts as
> both the NFS server scratch device and the server under test.
>
I believe Boyang has stated that this has been seen both in loopback
and in an externally mounted configuration.
Boyang, in your external exported configuration, was the lockup
happening on the client or server system?
- Ted
P.S. I just don't have the capability of testing NFS on separate VM's
for the client and server using gce-xfstests. It's on my list of
things to implement someday, but I just don't have time at the moment.
Maybe a GSOC project someday... Or if someone has time, patches or
pull requests to https://github.com/tytso/xfstests-bld are gratefully
accepted. :-)
next prev parent reply other threads:[~2022-07-21 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 2:29 [PATCH v1] generic/476: requires 27GB scratch size bxue
2022-07-21 2:49 ` xuyang2018.jy
2022-07-21 7:17 ` Boyang Xue
2022-07-21 4:40 ` Darrick J. Wong
2022-07-21 7:26 ` Boyang Xue
2022-07-21 11:42 ` Theodore Ts'o
2022-07-21 14:03 ` Theodore Ts'o
2022-07-21 15:12 ` Chuck Lever III
2022-07-21 15:14 ` Chuck Lever III
2022-07-21 18:04 ` Theodore Ts'o [this message]
2022-07-21 18:13 ` Chuck Lever III
2022-07-22 2:18 ` Theodore Ts'o
2022-08-04 9:10 ` Boyang Xue
2022-07-21 15:29 ` Zorro Lang
2022-07-21 15:32 ` Chuck Lever III
2022-07-21 16:30 ` Zorro Lang
2022-07-21 18:25 ` Jeff Layton
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=YtmVH8HNHHxVUyoM@mit.edu \
--to=tytso@mit.edu \
--cc=bxue@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@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