Re: (no subject)

[Jeff Layton <jlayton@redhat.com>]

On Thu, 02 Aug 2007 09:24:28 +0200
Piotr Kandziora <raveen@tlen.pl> wrote:

> Server NFS: 192.168.0.166
> client 1: 192.168.0.169
> client 2: 192.168.0.183
> 
> showmount output on server:
> # showmount -a
> All mount points on hostname:
> *:/aa
> *:/bb
> 192.168.0.169:*
> 192.168.0.183:*
> 
> # cat /var/lib/nfs/rmtab
> 192.168.0.183:*:0x00000001
> *:/aa:0x00000002
> 192.168.0.169:*:0x00000002
> *:/bb:0x00000002
> 
> client 1:
> # mount|grep 166
> 192.168.0.166:/aa on /mnt/tmp0 type nfs (rw,addr=192.168.0.166)
> 192.168.0.166:/bb on /mnt/tmp1 type nfs (rw,addr=192.168.0.166)
> 
> client 2:
> # mount|grep 166
> 192.168.0.166:/aa on /mnt/tmp0 type nfs
> (rw,vers=3,rsize=32768,wsize=32768,hard,proto=udp,timeo=7,retrans=3,addr=192.168.0.166)
> 
> On client 1 there are mounted two shares (aa and bb), on client 2 only one share (aa).
> 
> My questions are:
> 
> How to get information about mounted shares on concrete clients from showmount or other command?
> 

This info will never be reliable -- see the notes on rmtab in
rpc.mountd(8).

> What is meaning of asterisks in showmount output?

The nfs-utils rmtab handling code was recently fixed a few months ago.
You're likely running older code that's inserting these bogus entries
into the rmtab for each mount.

-- 
Jeff Layton <jlayton@redhat.com>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs