All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: lioupayphone <lioupayphone@gmail.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: what's the real meaning of fsid?
Date: Wed, 17 Dec 2008 17:32:07 -0500	[thread overview]
Message-ID: <49497DE7.6050102@RedHat.com> (raw)
In-Reply-To: <200812171336070316863@gmail.com>



lioupayphone wrote:
> Hello, everyone. 
> 
> fsid in /etc/exports was used for identifying a file system. if a file system which exported 2 directories, it seems that we should tag the two export entries with same fsid.
> 
> eg
> on one machine (server   10.10.37.147,  Centos5.2 with linux2.6.18):
> 
> #mkfs.ext3 /dev/sdc; mount /dev/sdc /mnt/;mkdir -p /mnt/dir1 /mnt/dir2; touch /mnt/dir1/wall-e /mnt/dir2/eva;
> #echo "/mnt/dir1 *(rw,async,root_squash,fsid=2)" > /etc/exports
> #echo "/mnt/dir2 *(rw,async,root_squash,fsid=2)" >> /etc/exports
> #service nfs start && exportfs -r
> 
> on another machine (client   10.10.37.154):
> #mount  10.10.37.147:/mnt/dir1 /mnt/1/ && mount 10.10.37.147:/mnt/dir2 /mnt/2/
> 
> i am puzzled:   on the client (10.10.37.154), i found both "/mnt/1/" and "/mnt/2/" have the same child ---- "wall-e".
> 
> so i browsed the code of 2.6.18 and found: exp_export(), fs/nfsd/export.c . i have taged a comment on this code listed below. please give me some suggestions. thx.
I'm a bit puzzled by "both "/mnt/1/" and "/mnt/2/" have the same child". 
Do mean they have the same file handle??

steved.



  reply	other threads:[~2008-12-17 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17  5:36 what's the real meaning of fsid? lioupayphone
2008-12-17 22:32 ` Steve Dickson [this message]
2008-12-18  1:16 ` lioupayphone
2008-12-18 15:21   ` Steve Dickson
2008-12-18 19:03 ` J. Bruce Fields
2008-12-19 15:04 ` lioupayphone

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=49497DE7.6050102@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lioupayphone@gmail.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 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.