Description of problem:
GFS(s) expects NFS fh_type and fh_len would have the same value.
This is apparently not correct. One obvious symptom is that
it will fail NFS V2 (which uses fixed fh_len for all requests)
Version-Release number of selected component (if applicable):
Depending on NFS request types - for v2 mount command, it fails
each time and every time.
Steps to Reproduce:
Mount GFS(s) partitions on NFS clients using NFS v2 protocol.
The command fails with ESTALE error.
Patch has submitted to cluster-devel list.
Patch submiited via:
In Steve's git tree on 02/23/07.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Devel ACK for 5.1 - Would like to get into an early 5.1 cycle kernel build.
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
It looks like we can now nfsv2 mount gfs filesystems, but once mounted it still
looks like we have problems:
[root@test158 mnt]# mount test183.test.redhat.com:/mnt/gfstest /mnt/test -o vers=2
[root@test158 mnt]# cd /mnt/test
[root@test158 test]# ls
[root@test158 test]# touch test
touch: setting times of `test': Stale NFS file handle
[root@test158 test]# ls -R
ls: reading directory ./linux-2.6.18.i686: Input/output error
[root@test158 test]# cat /proc/mounts | grep test183
test183.test.redhat.com:/mnt/gfstest /mnt/test nfs
Everything looked fine with nfsv3
Testing described in comment 7 was done with an i386 system running the -45
kernel hosting the gfs2 fs and acting as the nfs server. The nfs client machine
was x86_64 and running the -46 xen kernel.
Yes, nfs v3 does work but nfs v2 has been broken. It is not a high priority
at this moment.
I tried the same test as in comment 7 with the rhel5 ga kernel and didn't see
any difference in behavior.. i.e. the mount itself still succeds, however the
mounted fs isn't usable.
I'm not sure if this matches the exact behavior from before (the description
seems to imply that the mount command itself fails). Please advise if a new bug
should be opened to describe this behavior.
The good news is that nfs3 apperantly works with the -45 kernel (it panics my
system with -8)
Open a new bug for nfs v2 - mark this bug as verified
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.