Linux NFS development
 help / color / mirror / Atom feed
From: Chris Osicki <osk@admin.swisscom-mobile.ch>
To: Wendy Cheng <wcheng@redhat.com>
Cc: nfs@lists.sourceforge.net, Jason Keltz <jas@cse.yorku.ca>
Subject: Re: fsid question
Date: Thu, 29 Mar 2007 15:54:57 +0200	[thread overview]
Message-ID: <20070329155457.458bf8a9@slopi> (raw)
In-Reply-To: <46083474.8090906@redhat.com>

On Mon, 26 Mar 2007 17:00:36 -0400
Wendy Cheng <wcheng@redhat.com> wrote:

Hi

> Jason Keltz wrote:
> > Hi.
> >
> > I'm running a RedHat Enterprise 4 system.
> >
> > I have a question about the fsid option in /etc/exports that I was 
> > hoping someone might be able to help with.
> >
> > I am working with LVM under Linux.  If I export LVM volumes via NFS, the 
> > fsid is based on major/minor number.  
> This statement needs correction. An NFS fsid is not based on major/minor 
> numbers - it is is a 32 bit number that admin (root) can arbitrary 
> choose and use to uniquely identify an NFS export. More on this in the 
> following comment.

And this statement needs correction too ;-)
fsid _is_ based on major/minor number. I learned it the hard way,
seeing two filesystem swapped on NFS clients because of minor
number change after switching a cluster package to another node.

Then I read carefully fsid section in man 5 exports.

Regards,
Chris

[snip] 

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

  parent reply	other threads:[~2007-03-29 13:58 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
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 [this message]
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=20070329155457.458bf8a9@slopi \
    --to=osk@admin.swisscom-mobile.ch \
    --cc=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