From: Greg Banks Subject: Re: [PATCH] SGI 907674: document fsid export option Date: Tue, 24 Feb 2004 15:07:29 +1100 Sender: nfs-admin@lists.sourceforge.net Message-ID: <403ACE01.2BBF39D6@melbourne.sgi.com> References: <40188282.36FBA905@melbourne.sgi.com> <16442.51053.96888.392883@notabene.cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux NFS Mailing List Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1AvTrd-0002Va-4B for nfs@lists.sourceforge.net; Mon, 23 Feb 2004 20:08:09 -0800 Received: from mtvcafw.sgi.com ([192.48.171.6] helo=rj.sgi.com) by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.30) id 1AvTfO-0007kM-Qb for nfs@lists.sourceforge.net; Mon, 23 Feb 2004 19:55:30 -0800 To: Neil Brown Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: Neil Brown wrote: > > On Thursday January 29, gnb@melbourne.sgi.com wrote: > > G'day, > > > > This patch against nfs-utils 1.0.6 documents the fsid=num export > > option. > > Thanks. I've added a paragraph about the special meaning of fsid=0 > for NFSv4 and committed it to CVS. > Aha, it's embarrassment time. Since sending the patch I've discovered that this part > > +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. is wrong; the fsid passes through a dev_t interface and is silently truncated to 16 bits. The following fixes my gaffe. Sorry. --- utils/exportfs/exports.man.orig Tue Feb 24 15:06:35 2004 +++ utils/exportfs/exports.man Tue Feb 24 15:06:38 2004 @@ -277,7 +277,7 @@ 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 +block device on which the filesystem is mounted. Any 16 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 Greg. -- Greg Banks, R&D Software Engineer, SGI Australian Software Group. I don't speak for SGI. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs