Bug 461063 - NFS over GFS : fsid is required in /etc/exports; else -ESTALE
Summary: NFS over GFS : fsid is required in /etc/exports; else -ESTALE
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gfs
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Abhijith Das
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-03 22:01 UTC by Abhijith Das
Modified: 2010-01-12 03:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-16 11:15:11 UTC


Attachments (Terms of Use)

Description Abhijith Das 2008-09-03 22:01:39 UTC
If an nfs export of gfs does not set 'fsid' in /etc/exports on the server, the client mount fails with -ESTALE.

eg:
server: 
# cat /etc/exports
/mnt/gfs   <world>(rw,wdelay,no_root_squash,sync)

client
# mount server:/mnt/gfs /mnt/nfs
mount: stale NFS file handle

when I add fsid=1 to /etc/exports, i.e
/mnt/gfs   <world>(rw,wdelay,no_root_squash,fsid=1,sync)

client mount succeeds.

Should fsid be a mandatory param for NFS over GFS?

Comment 1 Steve Whitehouse 2008-12-10 16:40:50 UTC
Yes, it needs to be. We can't create filehandles from device numbers like local filesystems can, so we have this system of having to specify it. It ought to be documented though, so if its missing from the docs, then please turn this into a doc bug.

Potentially we might be able to create an ID by using the UUID or some other unique identifier in the future. The only problem being that we can never be sure that it will not be a duplicate of an existing one. The only really safe way is to get the user to specify it.


Note You need to log in before you can comment on or make changes to this bug.