From: Jakob Oestergaard <jakob@unthought.net>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: NFS/Kernel Problem: getfh failed: Operation not permitted
Date: Thu, 30 Mar 2006 18:41:40 +0200 [thread overview]
Message-ID: <20060330164140.GD9811@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0603301111421.738@chaos.analogic.com>
On Thu, Mar 30, 2006 at 11:14:11AM -0500, linux-os (Dick Johnson) wrote:
>
...
> Well NFS is supposed to work like this.
I know that (which is why I once spent a *long* time troubleshooting
this until someone told me that is was well known to cause flaky
behaviour on Linux - quite unlike Solaris in the same setup).
Anyway, it's a long time ago, and as I state initially, I don't know if
this is still a problem.
> If it doesn't, you may
> have some far more serious problems, perhaps duplicate IP addresses,
> etc., that prevent proper resolution and subsequent connections.
> It has nothing to do with luck.
Whatever you say.
--
/ jakob
next prev parent reply other threads:[~2006-03-30 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 13:19 NFS/Kernel Problem: getfh failed: Operation not permitted Justin Piszcz
2006-03-30 14:25 ` Trond Myklebust
2006-03-30 14:30 ` Justin Piszcz
2006-03-30 14:42 ` Trond Myklebust
2006-03-30 14:50 ` Justin Piszcz
2006-03-30 15:09 ` Trond Myklebust
2006-03-30 15:13 ` Justin Piszcz
2006-03-30 15:31 ` Jakob Oestergaard
2006-03-30 15:58 ` linux-os (Dick Johnson)
2006-03-30 16:05 ` Jakob Oestergaard
2006-03-30 16:14 ` linux-os (Dick Johnson)
2006-03-30 16:41 ` Jakob Oestergaard [this message]
2006-03-30 16:12 ` Trond Myklebust
2006-03-30 16:18 ` [NFS] " Steve Dickson
2006-03-30 16:51 ` Justin Piszcz
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=20060330164140.GD9811@unthought.net \
--to=jakob@unthought.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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