From: Alan Post <adp@prgmr.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: User process NFS write hang followed by automount hang requiring reboot
Date: Thu, 30 May 2019 18:22:03 -0600 [thread overview]
Message-ID: <20190531002203.GW4158@turtle.email> (raw)
In-Reply-To: <20190530183958.GA23001@fieldses.org>
On Thu, May 30, 2019 at 02:39:58PM -0400, J. Bruce Fields wrote:
> > > By the way, the above stack trace with "nfs_lock_and_join_requests"
> > > usually means that you are using a very small rsize or wsize (less than
> > > 4k). Is that the case? If so, you might want to look into just
> > > increasing the I/O size.
> > >
> >
> > These exports have rsize and wsize set to 1048576.
>
> Are you getting that from the mount commandline? It could be negotiated
> down during mount. I think you can get the negotiated values form the
> rsize= and wsize= values on the opts: line in /proc/self/mountstats.
> See also /proc/fs/nfsd/max_block_size.
>
Great catch. I was reporting configuration from the mount command-line.
I've spot checked /proc/self/mountstats and they report the same value,
rsize and wsize of 1048576. I do have different values for here for
NFS servers that are administratively outside of this cluster, where
it is 65536, but in those cases we're not setting that option on the
mount command-line and I am not experiencing the hang I report here
to those servers.
-A
--
Alan Post | Xen VPS hosting for the technically adept
PO Box 61688 | Sunnyvale, CA 94088-1681 | https://prgmr.com/
email: adp@prgmr.com
next prev parent reply other threads:[~2019-05-31 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 22:33 User process NFS write hang followed by automount hang requiring reboot Alan Post
2019-05-21 15:46 ` Trond Myklebust
2019-05-21 19:22 ` Alan Post
2019-05-30 18:39 ` J. Bruce Fields
2019-05-31 0:22 ` Alan Post [this message]
2019-05-24 17:31 ` Alan Post
2019-05-24 19:19 ` Trond Myklebust
2019-05-30 0:41 ` Alan Post
2019-05-30 1:09 ` Trond Myklebust
2019-06-04 17:44 ` Alan Post
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=20190531002203.GW4158@turtle.email \
--to=adp@prgmr.com \
--cc=bfields@fieldses.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;
as well as URLs for NNTP newsgroup(s).