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:52:57 -0500 [thread overview]
Message-ID: <20100302175257.GI5553@fieldses.org> (raw)
In-Reply-To: <0A63A1BA-F749-4CFF-B77D-98AEFC531035@gmail.com>
On Tue, Mar 02, 2010 at 06:20:43PM +0100, Anton Starikov wrote:
>
> On Mar 2, 2010, at 6:16 PM, J. Bruce Fields wrote:
>
> > 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?
>
> Server is Opensolaris.
>
> > That's pretty old kernel; I'd file a bug with CentOS.
>
> Unfortunately, with newer kernels this setup is even more problematic. :)
Any details?
As a rule, this list is probably going to be a better place to handle
bugs with the latest upstream kernels, and your distributor is more
likely to be useful for their kernels.
--b.
>
> >>
> >> 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?
>
> It always unfortunate, but last couple of days I can't get a hang :) Although nothing changed in setup, so it will happen anyway.
>
>
> Anton.
>
next prev parent reply other threads:[~2010-03-02 17:51 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
[not found] ` <0A63A1BA-F749-4CFF-B77D-98AEFC531035@gmail.com>
2010-03-02 17:52 ` J. Bruce Fields [this message]
[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=20100302175257.GI5553@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