NFS/Kernel Problem: getfh failed: Operation not permitted

NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

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?

Please CC as I am not on either list.

Thanks,

Justin.


-------------------------------------------------------
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

NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

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?

Please CC as I am not on either list.

Thanks,

Justin.

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Trond Myklebust]

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.

Are you still seeing this problem with 2.6 kernels with /proc/fs/nfsd
properly mounted?

Cheers,
  Trond

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

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
>

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Trond Myklebust]

On Thu, 2006-03-30 at 09:30 -0500, Justin Piszcz wrote:

> The kernel version in question is  2.4.21-31.ELa1smp.

I take it that the standard 'exportfs -rv' doesn't help? Normally, that
should suffice to stuff /proc/fs/nfs/exports with the entries
in /etc/exports.

Cheers,
  Trond

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

I tried an exportfs -rv and it did not help.  Any other suggestions?

On Thu, 30 Mar 2006, Trond Myklebust wrote:

> On Thu, 2006-03-30 at 09:30 -0500, Justin Piszcz wrote:
>
>> The kernel version in question is  2.4.21-31.ELa1smp.
>
> I take it that the standard 'exportfs -rv' doesn't help? Normally, that
> should suffice to stuff /proc/fs/nfs/exports with the entries
> in /etc/exports.
>
> Cheers,
>  Trond
>

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Trond Myklebust]

On Thu, 2006-03-30 at 09:50 -0500, Justin Piszcz wrote:
> I tried an exportfs -rv and it did not help.  Any other suggestions?

Did the output from 'exportfs -rv' match with the contents
of /etc/exports? If so, did it also match with the contents
of /var/lib/nfs/xtab and /proc/fs/nfs/exports?

Cheers,
  Trond

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

On Thu, 30 Mar 2006, Trond Myklebust wrote:

> On Thu, 2006-03-30 at 09:50 -0500, Justin Piszcz wrote:
>> I tried an exportfs -rv and it did not help.  Any other suggestions?
>
> Did the output from 'exportfs -rv' match with the contents
> of /etc/exports? If so, did it also match with the contents
> of /var/lib/nfs/xtab and /proc/fs/nfs/exports?
>
> Cheers,
>  Trond
>

In the /etc/exports file, I have an entry that looks like this:
/path	specific-host-001(ro,root_squash,no_sync)
/path	specific-host-002((ro,root_squash,no_sync)
/path	*(ro,root_squash,no_sync)

So while there are only three entries, there are:

cat /proc/fs/nfs/exports | wc -> 566
cat /var/lib/nfs/xtab | wc -> 564

Entries per file.

Is this more of a kernel or nfsutils issue at this point?



-------------------------------------------------------
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

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

On Thu, 30 Mar 2006, Trond Myklebust wrote:

> On Thu, 2006-03-30 at 09:50 -0500, Justin Piszcz wrote:
>> I tried an exportfs -rv and it did not help.  Any other suggestions?
>
> Did the output from 'exportfs -rv' match with the contents
> of /etc/exports? If so, did it also match with the contents
> of /var/lib/nfs/xtab and /proc/fs/nfs/exports?
>
> Cheers,
>  Trond
>

In the /etc/exports file, I have an entry that looks like this:
/path	specific-host-001(ro,root_squash,no_sync)
/path	specific-host-002((ro,root_squash,no_sync)
/path	*(ro,root_squash,no_sync)

So while there are only three entries, there are:

cat /proc/fs/nfs/exports | wc -> 566
cat /var/lib/nfs/xtab | wc -> 564

Entries per file.

Is this more of a kernel or nfsutils issue at this point?

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Jakob Oestergaard]

On Thu, Mar 30, 2006 at 10:13:38AM -0500, Justin Piszcz wrote:
> On Thu, 30 Mar 2006, Trond Myklebust wrote:
> 
...
> In the /etc/exports file, I have an entry that looks like this:
> /path	specific-host-001(ro,root_squash,no_sync)
> /path	specific-host-002((ro,root_squash,no_sync)
> /path	*(ro,root_squash,no_sync)

I don't know how this works today, but historically Linux has been
completely unable to deal with any kind of names in /etc/exports.
Netgroups, DNS names, ...  And the results have been the strangest mix
of things sort-of-mostly-but-not-quite working.

I'd put in IP addresses, netmasks or '*', and see if that solves the
problem.

Again, I don't know if this is related to what you're seeing, but I'd
say it's worth a shot :)

-- 

 / jakob

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[linux-os (Dick Johnson)]

On Thu, 30 Mar 2006, Jakob Oestergaard wrote:

> On Thu, Mar 30, 2006 at 10:13:38AM -0500, Justin Piszcz wrote:
>> On Thu, 30 Mar 2006, Trond Myklebust wrote:
>>
> ...
>> In the /etc/exports file, I have an entry that looks like this:
>> /path	specific-host-001(ro,root_squash,no_sync)
>> /path	specific-host-002((ro,root_squash,no_sync)
>> /path	*(ro,root_squash,no_sync)
>
> I don't know how this works today, but historically Linux has been
> completely unable to deal with any kind of names in /etc/exports.
> Netgroups, DNS names, ...  And the results have been the strangest mix
> of things sort-of-mostly-but-not-quite working.
>
> I'd put in IP addresses, netmasks or '*', and see if that solves the
> problem.
>
> Again, I don't know if this is related to what you're seeing, but I'd
> say it's worth a shot :)
>
> --

>
> / jakob
>


This is my /etc/exports and it works fine with linux-2.6.15.4.
All the host names are local, inside the firewall, and need to
be looked-up over a W$<crap> name-server.

#
/rmtboot/LinuxRoot	*(ro,async)
/root/Scanner	*(ro,no_root_squash,sync)
/tmp		*(rw,no_root_squash,sync)
/usr/src	quark(rw,no_root_squash,sync)
/usr/lib	quark(rw,no_root_squash,sync)
/home/hpbd	*(rw,no_root_squash,sync)
/exports	*(rw,no_root_squash,sync)
/home/project/boneserver	*(rw,no_root_squash,sync)
/root		groveland(rw,no_root_squash,sync)
/root		quark(rw,no_root_squash,sync)
/root/DAS	*(ro,no_root_squash,sync)
/dos/drive_C	*(ro,sync)
# End of exports.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips).
Warning : 98.36% of all statistics are fiction, book release in April.
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[linux-os (Dick Johnson)]

On Thu, 30 Mar 2006, Jakob Oestergaard wrote:

> On Thu, Mar 30, 2006 at 10:13:38AM -0500, Justin Piszcz wrote:
>> On Thu, 30 Mar 2006, Trond Myklebust wrote:
>>
> ...
>> In the /etc/exports file, I have an entry that looks like this:
>> /path	specific-host-001(ro,root_squash,no_sync)
>> /path	specific-host-002((ro,root_squash,no_sync)
>> /path	*(ro,root_squash,no_sync)
>
> I don't know how this works today, but historically Linux has been
> completely unable to deal with any kind of names in /etc/exports.
> Netgroups, DNS names, ...  And the results have been the strangest mix
> of things sort-of-mostly-but-not-quite working.
>
> I'd put in IP addresses, netmasks or '*', and see if that solves the
> problem.
>
> Again, I don't know if this is related to what you're seeing, but I'd
> say it's worth a shot :)
>
> --
>
> / jakob
>


This is my /etc/exports and it works fine with linux-2.6.15.4.
All the host names are local, inside the firewall, and need to
be looked-up over a W$<crap> name-server.

#
/rmtboot/LinuxRoot	*(ro,async)
/root/Scanner	*(ro,no_root_squash,sync)
/tmp		*(rw,no_root_squash,sync)
/usr/src	quark(rw,no_root_squash,sync)
/usr/lib	quark(rw,no_root_squash,sync)
/home/hpbd	*(rw,no_root_squash,sync)
/exports	*(rw,no_root_squash,sync)
/home/project/boneserver	*(rw,no_root_squash,sync)
/root		groveland(rw,no_root_squash,sync)
/root		quark(rw,no_root_squash,sync)
/root/DAS	*(ro,no_root_squash,sync)
/dos/drive_C	*(ro,sync)
# End of exports.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips).
Warning : 98.36% of all statistics are fiction, book release in April.
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Jakob Oestergaard]

On Thu, Mar 30, 2006 at 10:58:08AM -0500, linux-os (Dick Johnson) wrote:
...
> This is my /etc/exports and it works fine with linux-2.6.15.4.
> All the host names are local, inside the firewall, and need to
> be looked-up over a W$<crap> name-server.
> 
> #
> /rmtboot/LinuxRoot	*(ro,async)
> /root/Scanner	*(ro,no_root_squash,sync)
> /tmp		*(rw,no_root_squash,sync)
> /usr/src	quark(rw,no_root_squash,sync)
> /usr/lib	quark(rw,no_root_squash,sync)
...

Well lucky you  :)

I'm not saying it can't work. I'm just saying I've spent too much time
finding out the hard way that it does not necessarily work  :)

-- 

 / jakob



-------------------------------------------------------
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

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Jakob Oestergaard]

On Thu, Mar 30, 2006 at 10:58:08AM -0500, linux-os (Dick Johnson) wrote:
...
> This is my /etc/exports and it works fine with linux-2.6.15.4.
> All the host names are local, inside the firewall, and need to
> be looked-up over a W$<crap> name-server.
> 
> #
> /rmtboot/LinuxRoot	*(ro,async)
> /root/Scanner	*(ro,no_root_squash,sync)
> /tmp		*(rw,no_root_squash,sync)
> /usr/src	quark(rw,no_root_squash,sync)
> /usr/lib	quark(rw,no_root_squash,sync)
...

Well lucky you  :)

I'm not saying it can't work. I'm just saying I've spent too much time
finding out the hard way that it does not necessarily work  :)

-- 

 / jakob

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[linux-os (Dick Johnson)]

On Thu, 30 Mar 2006, Jakob Oestergaard wrote:

> On Thu, Mar 30, 2006 at 10:58:08AM -0500, linux-os (Dick Johnson) wrote:
> ...
>> This is my /etc/exports and it works fine with linux-2.6.15.4.
>> All the host names are local, inside the firewall, and need to
>> be looked-up over a W$<crap> name-server.
>>
>> #
>> /rmtboot/LinuxRoot	*(ro,async)
>> /root/Scanner	*(ro,no_root_squash,sync)
>> /tmp		*(rw,no_root_squash,sync)
>> /usr/src	quark(rw,no_root_squash,sync)
>> /usr/lib	quark(rw,no_root_squash,sync)
> ...
>
> Well lucky you  :)
>
> I'm not saying it can't work. I'm just saying I've spent too much time
> finding out the hard way that it does not necessarily work  :)
>
> --

>
> / jakob
>

Well NFS is supposed to work like this. 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.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips).
Warning : 98.36% of all statistics are fiction, book release in April.
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[linux-os (Dick Johnson)]

On Thu, 30 Mar 2006, Jakob Oestergaard wrote:

> On Thu, Mar 30, 2006 at 10:58:08AM -0500, linux-os (Dick Johnson) wrote:
> ...
>> This is my /etc/exports and it works fine with linux-2.6.15.4.
>> All the host names are local, inside the firewall, and need to
>> be looked-up over a W$<crap> name-server.
>>
>> #
>> /rmtboot/LinuxRoot	*(ro,async)
>> /root/Scanner	*(ro,no_root_squash,sync)
>> /tmp		*(rw,no_root_squash,sync)
>> /usr/src	quark(rw,no_root_squash,sync)
>> /usr/lib	quark(rw,no_root_squash,sync)
> ...
>
> Well lucky you  :)
>
> I'm not saying it can't work. I'm just saying I've spent too much time
> finding out the hard way that it does not necessarily work  :)
>
> --
>
> / jakob
>

Well NFS is supposed to work like this. 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.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips).
Warning : 98.36% of all statistics are fiction, book release in April.
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Jakob Oestergaard]

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

Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Trond Myklebust]

On Thu, 2006-03-30 at 10:13 -0500, Justin Piszcz wrote:
> On Thu, 30 Mar 2006, Trond Myklebust wrote:
> 
> > On Thu, 2006-03-30 at 09:50 -0500, Justin Piszcz wrote:
> >> I tried an exportfs -rv and it did not help.  Any other suggestions?
> >
> > Did the output from 'exportfs -rv' match with the contents
> > of /etc/exports? If so, did it also match with the contents
> > of /var/lib/nfs/xtab and /proc/fs/nfs/exports?
> >
> > Cheers,
> >  Trond
> >
> 
> In the /etc/exports file, I have an entry that looks like this:
> /path	specific-host-001(ro,root_squash,no_sync)
> /path	specific-host-002((ro,root_squash,no_sync)
> /path	*(ro,root_squash,no_sync)
> 
> So while there are only three entries, there are:
> 
> cat /proc/fs/nfs/exports | wc -> 566
> cat /var/lib/nfs/xtab | wc -> 564

Yes, but do they match? /var/lib/nfs/xtab and /proc/fs/nfs/exports are
supposed to differ in that 'exportfs' will fill in a few default
options. The question is whether there are entries for
specific-host-001, specific-host-002,...

> Entries per file.
> 
> Is this more of a kernel or nfsutils issue at this point?

More likely to be an nfs-utils issue.

Cheers,
  Trond

Re: Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Steve Dickson]

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

Re: [NFS] Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Steve Dickson]

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.

Re: Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

Thanks, I will give this a try sometime soon and hopefully it'll fix the 
issue :)

Justin.

On Thu, 30 Mar 2006, Steve Dickson wrote:

> 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

Re: [NFS] Re: NFS/Kernel Problem: getfh failed: Operation not permitted

[Justin Piszcz]

Thanks, I will give this a try sometime soon and hopefully it'll fix the 
issue :)

Justin.

On Thu, 30 Mar 2006, Steve Dickson wrote:

> 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.
>