From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: NFS/Kernel Problem: getfh failed: Operation not permitted
Date: Thu, 30 Mar 2006 09:30:56 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603300929340.18696@p34> (raw)
In-Reply-To: <1143728720.8074.41.camel@lade.trondhjem.org>
On Thu, 30 Mar 2006, Trond Myklebust wrote:
> On Thu, 2006-03-30 at 08:19 -0500, Justin Piszcz wrote:
>> The error is: rpc.mountd: getfh failed: Operation not permitted
>>
>> In order to fix this error, someone needs to run these commands on each
>> nfs server.
>>
>> 40 service nfs stop
>> 41 rm -f /var/lib/nfs/etab /var/lib/nfs/rmtab /var/lib/nfs/state
>> /var/lib/xtab
>> 42 touch /var/lib/nfs/etab /var/lib/nfs/rmtab /var/lib/nfs/state
>> /var/lib/xtab
>> 43 chmod 644 /var/lib/nfs/etab /var/lib/nfs/rmtab /var/lib/nfs/state
>> /var/lib/xtab
>> 44 service nfs start
>>
>> http://www.ccs.neu.edu/home/johan/personal/linux.html
>>
>> This issue seems to be more of an NFS issue than a kernel one, but I was
>> wondering what other people had to say about it. There are a lot of
>> responses and questions concerning this error on google, but VERY few
>> people have a response or method of fixing it, much less finding a
>> permanent fix.
>>
>> Has anyone found a fix or work-around that does not require restarting
>> NFS?
>
> Very few people ought to be running RH-9 out there given that the
> official support expired several years ago.
Not running RH9, but running RHEL WS3, Taroon Update 4, however, the
nfs-utils is 1.0.6-33EL, I know there were many fixes in 1.0.7+, could
nfs-utils be the problem? The kernel version in question is
2.4.21-31.ELa1smp.
>
> Are you still seeing this problem with 2.6 kernels with /proc/fs/nfsd
> properly mounted?
Not using 2.6.
>
> Cheers,
> Trond
>
next prev parent reply other threads:[~2006-03-30 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 13:19 Justin Piszcz
2006-03-30 14:25 ` Trond Myklebust
2006-03-30 14:30 ` Justin Piszcz [this message]
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
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=Pine.LNX.4.64.0603300929340.18696@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®