Re: what's the real meaning of fsid?

[Steve Dickson <SteveD@redhat.com>]

lioupayphone wrote:
>>
> yes, both the two directories have a same FH.
> when i "cat /proc/fs/nfsd/exports ", it shows :
> # Version 1.1
> # Path Client(Flags) # IPs
> /mnt/dir1       *(rw,root_squash,async,wdelay,no_subtree_check,fsid=2)
> /mnt/dir2       *(rw,root_squash,async,wdelay,no_subtree_check,fsid=2) 
> 
> and i "rpc.mountd -d all", and try do mount on client: 
> 	mount -t nfs -o nolock 10.10.37.147:/mnt/dir1 /mnt/1/; 
> 	mount -t nfs -o nolock 10.10.37.147:/mnt/dir2 /mnt/2/;
> 
> in kernel, /mnt/dir1 and /mnt/dir2 respectively corresponds to   two different svc_export objects. 
> in fh_compose(), they have same fsid_type and fsid, but the fileidtype and fileid should NOT be same.
> i am still in puzzled. :-(

The reason your getting the same file handle for both mounts is 
because the 'fsid=2' is set on both exports. So what is happening 
is the 'mount 10.10.37.147:/mnt/dir2 /mnt/2' is actually mounting 
the /mnt/1 directory on the server which is the reason for the
same file handle.  At least that's what as happening in my testing. 

So you have two options. One, don't set the fsid or don't make the fsids
the same value.

steved.