From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anton Starikov <ant.starikov@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv3/NFSv4 problem.
Date: Tue, 2 Mar 2010 12:16:14 -0500 [thread overview]
Message-ID: <20100302171614.GH5553@fieldses.org> (raw)
In-Reply-To: <D27EC8DD-AD1C-432D-99FD-E4AB6C26D189@gmail.com>
On Mon, Mar 01, 2010 at 04:01:42PM +0100, Anton Starikov wrote:
> Hi,
>
>
> my config is diskless NFSv3 nfsroot (+ some extra NFDSv3 mounts) and NFSv4 /home/* automount.
> Centos 5.4, kernel 2.6.18-164.11.1.el5.
That's the client? What's the server?
That's pretty old kernel; I'd file a bug with CentOS.
> Periodically my nodes hangs, nothing appeared in the logs (remote syslog + netconsole).
> Node is kind of alive, you can ping, some deamons (for example pbs_mom) reports that it's alive etc.
> But anything which require FS access - frozen.
>
> Another symptom, it looks like portmap doesn't answer. At lease if I try "rpcinfo -p node_name", then it ends with
> "rpcinfo: can't contact portmapper: rpcinfo: RPC: Timed out"
>
> In principal, this can have something with locking.
> At least, I had to mount all my NFSv3 mounts with nolock, to reduce frequency of problem (nfsroot was nolock, obviously. but there are couple of extra v3 mounts, like /opt with extra software and RW directory for torque.
>
> What can be a problem here?
>
> What kind of information I have to collect from system to figure out what it real problem?
Is there any server-side logging?
Can you see any interesting network traffic after the hang?
--b.
next prev parent reply other threads:[~2010-03-02 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 15:01 NFSv3/NFSv4 problem Anton Starikov
2010-03-02 17:16 ` J. Bruce Fields [this message]
[not found] ` <0A63A1BA-F749-4CFF-B77D-98AEFC531035@gmail.com>
2010-03-02 17:52 ` J. Bruce Fields
[not found] ` <F4A02563-59B0-4A9B-B773-4FCF5FD2A8D4@gmail.com>
2010-03-03 15:45 ` J. Bruce Fields
2010-03-04 13:36 ` Anton Starikov
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=20100302171614.GH5553@fieldses.org \
--to=bfields@fieldses.org \
--cc=ant.starikov@gmail.com \
--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