>This message usually means that NFS server and client do not agree on
>the version of NFS offered, however this might not be the cause of your
>problems.
>So, could you login as root to the RHEL3 boxes and do an:
>rpcinfo -p server (server=resolvable name of your RHEL5).
>and provide the output?
Sure. Here it is:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 662 status
100024 1 tcp 662 status
100011 1 udp 875 rquotad
100011 2 udp 875 rquotad
100011 1 tcp 875 rquotad
100011 2 tcp 875 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
100021 1 tcp 32803 nlockmgr
100021 3 tcp 32803 nlockmgr
100021 4 tcp 32803 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 892 mountd
100005 1 tcp 892 mountd
100005 2 udp 892 mountd
100005 2 tcp 892 mountd
100005 3 udp 892 mountd
100005 3 tcp 892 mountd
>Also, what are the mount options you use on the /etc/fstab file (or
>automount config) on the RHEL3 side to mount the home dirs from RHEL5?
On the RHEL 3 side, I have in /etc/fstab:
sapphire:/home /home nfs rw 0 0
>Do the NFS imported partitions show up in df, does it hang, display the
>partitions as mounted but with no util info?...
Doing a df shows the partitions. Everything looks fine:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 151739168 96917132 47114052 68% /
/dev/sda1 46636 34217 10011 78% /boot
none 509440 0 509440 0% /dev/shm
sapphire:/products 10321216 8222048 1574944 84% /products
scifs:/users 209715200 138025344 67381216 68% /users
scifs:/databases 129653504 103550880 24471296 81% /databases
/dev/ramdisk 7931 13 7918 1% /mnt/ramdisk
sapphire:/home 30472192 21363488 7536192 74% /home
scifs is another machine (SunOS) who isn't affected in anyway.
It definately has something to do with the nfs version being used. If I
explicitly change the entry in /etc/fstab to:
sapphire:/home /home nfs rw,vers=2 0 0
the input/output error goes away. Could it be a patch to nfs in RHEL 5
changed something to cause this?
Ryan
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
