Linux NFS development
 help / color / mirror / Atom feed
From: Jason Keltz <jas@cse.yorku.ca>
To: James Pearson <james-p@moving-picture.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: fsid question
Date: Tue, 27 Mar 2007 09:29:37 -0400	[thread overview]
Message-ID: <46091C41.6070908@cse.yorku.ca> (raw)
In-Reply-To: <46091498.6030706@moving-picture.com>

On 03/27/07 08:56, James Pearson wrote:
> Jason Keltz wrote:
>> 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?
> 
> I believe you can add a fsid to /etc/exports and re-export the file 
> systems - existing mounts will not be affected. New mounts will pick up 
> the new fsid. The existing mounts will also pick up the new fsid the 
> next time they remount the file system.
> 
> I've certainly done this in the past and had no problems.
> 
> James Pearson

Hi James.

Thanks for your message.

I'm not sure that I understand this though.  If the system is generating 
an fsid for NFS exports in the absence of a user-specified fsid, then 
changing the fsid and re-exporting the filesystem *should* essentially 
confuse the client? How does one choose an fsid that is not already in 
use on the system? I imagine there must be some way to list the 
currently used fsids for exported filesystems.

Jas.

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-03-27 13:29 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
2007-03-27 12:56     ` James Pearson
2007-03-27 13:29       ` Jason Keltz [this message]
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=46091C41.6070908@cse.yorku.ca \
    --to=jas@cse.yorku.ca \
    --cc=james-p@moving-picture.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox