Re: Getting RPC Error 88



It appears you're running Oracle Linux with Oracle's Unbreakable
Enterprise Kernel (UEK) [0] which is not compatible with RHEL's standard
kernel [1] nor is it the kernel that goes through the same level of testing
and compliance as a tier 1 operating system validation with the major
hardware vendors [2]. I would suggest either rebooting into the standard
RHEL compatible kernel (it will be a 2.6.18 kernel), filing a ticket
with Oracle about the issue you're facing, or migrate back to real RHEL ;)


-AdamM

[0] http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/kernel-uek-2.6.32-300.4.1.el5uek.x86_64.rpm
[1] http://ftp.redhat.com/redhat/linux/enterprise/5Server/en/os/SRPMS/kernel-2.6.18-308.4.1.el5.src.rpm
[2] http://www.redhat.com/rhel/compatibility/hardware/

On Thu, May 17, 2012 at 11:01:22AM -0500, Rhugga Harper wrote:
We have a 2-node Oracle RAC that keeps getting the following error:
kernel: nfs: RPC call returned error 88

The storage being mounted is netapp. We don't see any errors/issues on the
storage itself or the switches this client is connecting thru. The NFS
network is a 2-interface ( 2 x 1Gb UTP) bond which shows no errors of any
kind.

We are mounting with the following mount options:
rw,noac,nointr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tcp

This problem sometimes hits the OCR votedisk shares and causes the instance
to crash.

These systems were upgraded to 5.6 back in January.

Currently running 2.6.32-300.4.1.

Thanks for any info,
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Re: Accessing memory at 0xb800
    ... FYI, "10h" isn't a standard hardware interrupt, it's a BIOS interrupt. ... Unless you're hacking your kernel, kiss your BIOS interrupts goodbye, ... a privileged mode, you basically have to write your own kernel (or hack ...
    (alt.comp.lang.learn.c-cpp)
  • Re: Accessing memory at 0xb800
    ... FYI, "10h" isn't a standard hardware interrupt, it's a BIOS interrupt. ... Unless you're hacking your kernel, kiss your BIOS interrupts goodbye, ... a privileged mode, you basically have to write your own kernel (or hack ...
    (comp.lang.cpp)
  • Re: [PATCH 6/6] sched: disabled rt-bandwidth by default
    ... For this, if this time limit does kick in, we should at the very least ... The kernel should not set policy but provide capabilities. ... really good reason to show why the standard is wrong. ...
    (Linux-Kernel)
  • Re: Why bigForth is Linux only
    ... different operating systems. ... They differ _very_ much at the kernel ... Because some 20 year old standard mandates that? ...
    (comp.lang.forth)
  • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
    ... > Matthew Wilcox wrote: ... others would like a true "install" with copying files so that they can delete ... the kernel sources anytime they do want. ... Does that header belong to the international C99 Standard? ...
    (Linux-Kernel)