From: neilbrown <neilbrown>
Date: Tue, 24 Feb 2004 03:32:30 +0000 (+0000)
Subject: Document fsid=
X-Git-Tag: nfs-utils-1-0-6-post1^0
X-Git-Url: https://git.decadent.org.uk/gitweb/?p=nfs-utils.git;a=commitdiff_plain;h=7b8b7f8f47892f38432fda434ea8d84fa87a9360;hp=b7f4ad19f9b3b8e0f93da719a86d0e865be5ab75

Document fsid=
---

diff --git a/ChangeLog b/ChangeLog
index 04128ad..2c49a61 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2004-02-24 NeilBrown <neilb@cse.unsw.edu.au>
+	Based on patch from  Greg Banks <gnb@melbourne.sgi.com>
+
+	* utils/exportfs/exports.man: Document fsid= option.
+	
 2003-09-15 NeilBrown <neilb@cse.unsw.edu.au>
 
 	Release 1.0.6
diff --git a/utils/exportfs/exports.man b/utils/exportfs/exports.man
index 6223944..034a896 100644
--- a/utils/exportfs/exports.man
+++ b/utils/exportfs/exports.man
@@ -256,6 +256,28 @@ If a path is given (e.g.
 then the nominted path must be a mountpoint for the exportpoint to be
 exported.
 
+.TP
+.IR fsid= num
+This option forces the filesystem identification portion of the file
+handle and file attributes used on the wire to be
+.I num
+instead of a number derived from the major and minor number of the
+block device on which the filesystem is mounted.  Any 32 bit number
+can be used, but it must be unique amongst all the exported filesystems.
+
+This can be useful for NFS failover, to ensure that both servers of
+the failover pair use the same NFS file handles for the shared filesystem
+thus avoiding stale file handles after failover.
+
+Some Linux filesystems are not mounted on a block device; exporting
+these via NFS requires the use of the
+.I fsid
+option (although that may still not be enough).
+
+The value  0 has a special meaning when use with NFSv4.  NFSv4 has a
+concept of a root of the overall exported filesystem. The export point
+exported with fsid=0 will be used as this root.
+
 .SS User ID Mapping
 .PP
 .I nfsd