All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: Re: NFS/Kernel Problem: getfh failed: Operation not permitted
Date: Thu, 30 Mar 2006 11:18:06 -0500	[thread overview]
Message-ID: <442C04BE.5000602@RedHat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603300929340.18696@p34>

Justin Piszcz wrote:
> 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.
Try updating your nfs-utils to 1.0.6-43EL....

steved.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

WARNING: multiple messages have this Message-ID (diff)
From: Steve Dickson <SteveD@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: NFS/Kernel Problem: getfh failed: Operation not permitted
Date: Thu, 30 Mar 2006 11:18:06 -0500	[thread overview]
Message-ID: <442C04BE.5000602@RedHat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603300929340.18696@p34>

Justin Piszcz wrote:
> 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.
Try updating your nfs-utils to 1.0.6-43EL....

steved.

  parent reply	other threads:[~2006-03-30 16:18 UTC|newest]

Thread overview: 22+ 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 13:19 ` 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:13             ` Justin Piszcz
2006-03-30 15:31             ` Jakob Oestergaard
2006-03-30 15:58               ` linux-os (Dick Johnson)
2006-03-30 15:58                 ` linux-os (Dick Johnson)
2006-03-30 16:05                 ` Jakob Oestergaard
2006-03-30 16:05                   ` Jakob Oestergaard
2006-03-30 16:14                   ` linux-os (Dick Johnson)
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     ` Steve Dickson [this message]
2006-03-30 16:18       ` [NFS] " Steve Dickson
2006-03-30 16:51       ` Justin Piszcz
2006-03-30 16:51         ` [NFS] " 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=442C04BE.5000602@RedHat.com \
    --to=steved@redhat.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.