From: Michael O'Donnell <modonnell-kx56TfycDUc@public.gmane.org>
To: Dennis Nezic <dennisn-YN8wfZw00oOZ9vWoFJJngh2eb7JE58TQ@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS stops responding
Date: Mon, 19 Apr 2010 10:34:12 -0400 [thread overview]
Message-ID: <4BCC69E4.70405@wsi.com> (raw)
In-Reply-To: <20100416201700.215b0bea.dennisn-YN8wfZw00oOZ9vWoFJJngh2eb7JE58TQ@public.gmane.org>
Well, it's encouraging to finally get a response and even more so that
you may be seeing the same kinds of failures. I will post logging output
from /var/log/messages from the client and server machines while the
failures are occurring and maybe we can compare notes?
Dennis Nezic wrote:
> Well I for one am convinced there is a bug either in the linux kernel,
> or somewhere. I have a similar problem (I posted about it here on March
> 18 2010), where NFS activity very frequently hangs for several minutes,
> for no good reason. (Changing the nfs mount option to "hard" should get
> rid of the I/O Errors, but it's still incredibly frustrating/annoying
> -- it will simply retry after precious minutes have been wasted, instead
> of failing :b). My problems began ONLY after I upgraded my server's
> kernel. When did yours begin?
>
> I have noticed that when a client hangs, other clients still work --
> ie. the nfs server is still (sortof) working -- so I imagine there is
> something wrong with the client too?
>
next prev parent reply other threads:[~2010-04-19 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 21:06 NFS stops responding Michael O'Donnell
2010-04-15 18:04 ` J. Bruce Fields
2010-04-17 0:17 ` Dennis Nezic
[not found] ` <20100416201700.215b0bea.dennisn-YN8wfZw00oOZ9vWoFJJngh2eb7JE58TQ@public.gmane.org>
2010-04-19 14:34 ` Michael O'Donnell [this message]
[not found] ` <4BCC69E4.70405-kx56TfycDUc@public.gmane.org>
2010-04-22 15:19 ` Dennis Nezic
2010-04-28 15:51 ` Dennis Nezic
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 13:39 Douglas Furlong
2004-09-30 16:06 ` Jason Holmes
2004-09-30 19:10 ` Jason Holmes
2004-10-01 15:40 ` Jason Holmes
2004-10-07 10:56 ` Douglas Furlong
2004-10-13 15:07 ` Jason Holmes
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=4BCC69E4.70405@wsi.com \
--to=modonnell-kx56tfycduc@public.gmane.org \
--cc=dennisn-YN8wfZw00oOZ9vWoFJJngh2eb7JE58TQ@public.gmane.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