From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: git <8f6576a> Causes non-interruptible stalls in NFS clients
Date: Thu, 31 May 2012 05:01:01 -0700 [thread overview]
Message-ID: <4FC75D7D.6060002@gmail.com> (raw)
Merge: 8f6576a cc0a984
Author: Linus Torvalds
Date: Tue May 29 10:43:51 2012 -0700
Merge tag 'nfs-for-3.5-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs
Pull NFS client updates from Trond Myklebust:
- Improve the code sharing between NFSv2/v3 and v4 mounts
That last comment gave me the idea to enable NFSv4 client support in my kernel
(which I had disabled many months ago because of NFSv4 weirdness).
Enabling NFSv4 client support completely fixed the non-interruptible NFS stalls
and, strangely, also fixed the very similar stalls in my scp/sftp clients when
pushing files > 800KB or so.
Enabling the NFSv4 client support fixes everything even though I'm still using
NFSv3 mounts explicitly/exclusively.
reply other threads:[~2012-05-31 12:01 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=4FC75D7D.6060002@gmail.com \
--to=w41ter@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.