From: Jason Keltz <jas@cse.yorku.ca>
To: Wendy Cheng <wcheng@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: fsid question
Date: Tue, 27 Mar 2007 08:50:45 -0400 [thread overview]
Message-ID: <46091325.6050403@cse.yorku.ca> (raw)
In-Reply-To: <46083474.8090906@redhat.com>
Hi Wendy,
Thanks for your response..
A few more comments...
On 03/26/07 17:00, Wendy Cheng wrote:
> Jason Keltz wrote:
>> 1) How do I find out the fsid of an existing export so that I can
>> "hard-code" it in the /etc/exports file?
>>
> The admin (root, or whoever has access rights to /etc/exports file) can
> pick one number between 0 and 0xffffffff and add it into /etc/exports.
> It comes and goes with each "exportfs" command. This id is used to
> construct NFS filehandle that will be sent to NFS client upon requests.
> NFS client uses file handle to communicate with NFS server on which file
> they want to have access. The fsid, if specified, is part of the file
> handle that uniquely identifies an export (one entry in /etc/exports file).
>
> So as rule of thumb, you would not want to change fsid as long as there
> are NFS clients still out there trying to access the files on the
> server. It is, however, not a permanent ID since there is no filesystem
> "on-disk" record of it.
The problem is that right now, I have several hundred clients who have
mounted the exported filesystems via NFS where I did not specify an
explicit fsid in the NFS sever /etc/exports file. In order to start
using the fsid option, I need to know the existing fsids so that I can
hard-code those into /etc/exports. This way, if the server is rebooted,
the clients will not be affected. I could then choose fsids for NEW nfs
exported filesystems and hard-code those fsids into /etc/exports. Is
there a Linux command, or an entry in /proc on the file server that will
let me know the existing fsids?
>> 3) What is the best way for me to generate my own fsid?
>>
> It is a number picked by admin and must be between 0 and 0xFFFFFFFF.
>
Is the fsid specified in hex?
Since the system will allocate its own fsid for NFS exported filesystems
that do not have a user-specified fsid, how do I choose fsids for my
user-specified fsid exports that will not conflict with those that the
system will use?
Thanks,
Jason.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-27 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 20:29 fsid question Jason Keltz
2007-03-26 21:00 ` Wendy Cheng
2007-03-27 12:50 ` Jason Keltz [this message]
2007-03-27 12:56 ` James Pearson
2007-03-27 13:29 ` Jason Keltz
2007-03-27 14:27 ` James Pearson
2007-03-27 14:57 ` Jason Keltz
2007-03-27 15:05 ` J. Bruce Fields
2007-03-27 14:52 ` Wendy Cheng
2007-03-27 15:23 ` J. Bruce Fields
2007-03-27 15:32 ` Trond Myklebust
2007-03-27 15:31 ` Roger Heflin
2007-03-29 13:54 ` Chris Osicki
2007-03-29 14:23 ` Wendy Cheng
[not found] <mailman.7028.1175219061.5558.nfs@lists.sourceforge.net>
2007-03-30 6:38 ` Klaus Steinberger
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=46091325.6050403@cse.yorku.ca \
--to=jas@cse.yorku.ca \
--cc=nfs@lists.sourceforge.net \
--cc=wcheng@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox