From: James Pearson <james-p@moving-picture.com>
To: mehta kiran <kiranmehta1981@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: file :"/var/lib/nfs/rmtab"
Date: Thu, 03 Feb 2005 11:29:25 +0000 [thread overview]
Message-ID: <42020B15.4030602@moving-picture.com> (raw)
In-Reply-To: <20050203060844.3898.qmail@web51603.mail.yahoo.com>
mehta kiran wrote:
> Hi ,
> In mountd man page , it written that
> rmtab is ornamental and client can contiune
> to use filesystem even after calling umount
> for that filesystem.
>
> Is there any real use of this rmtab file ?
> Does mountd use this file to know the
> clients having access to filesystem ?
> If yes , isn,t filehandle supplied by
> client enough to prove that client has access
> to filesystem. ?
On 2.4 kernels it is not 'ornamental' - if the server reboots without an
entry for a client mount in /var/lib/nfs/rmtab, then the client will get
a stale NFS file handle when the server reboots. This can happen if
umount fails e.g. the mount point is busy - rpc.mountd on the server
removes the entry from /var/lib/nfs/rmtab, but umount fails, so the file
system remains mounted.
I believe the situation has changed with 2.6.
James Pearson
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-03 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 6:08 file :"/var/lib/nfs/rmtab" mehta kiran
2005-02-03 11:29 ` James Pearson [this message]
2005-02-03 11:38 ` mehta kiran
2005-02-03 16:04 ` Paul Clements
2005-02-04 4:52 ` mehta kiran
2005-02-04 5:01 ` mehta kiran
2005-02-04 10:04 ` James Pearson
2005-02-04 10:55 ` mehta kiran
2005-02-04 12:58 ` James Pearson
2005-02-04 13:22 ` mehta kiran
2005-02-04 14:57 ` James Pearson
2005-02-04 15:49 ` mehta kiran
2005-02-04 15:49 ` mehta kiran
2005-02-04 14:07 ` mehta kiran
2005-02-03 11:38 ` mehta kiran
2005-02-03 11:42 ` mehta kiran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42020B15.4030602@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=kiranmehta1981@yahoo.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.