All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Sharp <andy@ccpu.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: nfs exporting my stacked fs
Date: Wed, 28 May 2003 22:29:22 -0700	[thread overview]
Message-ID: <20030529052922.GA4324@ccpu.com> (raw)
In-Reply-To: <16085.16577.463731.505824@notabene.cse.unsw.edu.au>

On Thu, May 29, 2003 at 09:05:37AM +1000, Neil Brown wrote:
> On Wednesday May 28, andy@ccpu.com wrote:
> > I could use some help getting my stacked (I guess that's the term d' jour)
> > file system to be nfs exported/mounted.  From reading the code, it seems
> > that my file system either has to require a device, it doesn't, or it
> > has to have some sort of FSID (the call to nfsctl_export() is failing),
> > only I can't seem to figure out how to accomplish that.  I tried to go
> > through the mountd source, but came up empty.  What did I miss?
> 
> If your filesystem isn't device based (which seems likely for a
> stacked filesystem), the nfsd cannot use the device number as a short,
> fixed length identifier for the filesystem, which it needs for storing
> in the filehandle.  So, you need to provide one.
> This is done in the /etc/exportss file with the fsid= option.
> e.g.
> 
>  /my/file/system myclient(rw,no_root_squash,sync,fsid=27)

Thanks for that info, I was unaware of that option.  Soooo, this brings
up some other questions for me.

What is the relation between the fsid option mentioned above and the
fsid returned by statfs op?  Which I discovered shortly after sending my
first email.  Should they match?  The i_dev is apparently used on device
datasets for the filehandle, so do all datasets with the same i_dev
somehow guarantee that i_dev/inode # 'filehandles' are somehow unique?

a


  reply	other threads:[~2003-05-29  5:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 21:57 nfs exporting my stacked fs Andrew Sharp
2003-05-28 23:05 ` Neil Brown
2003-05-29  5:29   ` Andrew Sharp [this message]
2003-05-30  4:04     ` Neil Brown
2003-05-30  8:20       ` Trond Myklebust
2003-05-30 16:24       ` Bryan Henderson
2003-05-30 23:10         ` Trond Myklebust
2003-05-30 23:30           ` Andrew Sharp
2003-05-30 23:44             ` Trond Myklebust
2003-05-31  0:12           ` Bryan Henderson
2003-05-31  2:44             ` Trond Myklebust
2003-06-02 16:13               ` Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
2003-06-05 15:38 David Chow
2003-06-05 16:30 ` Bryan Henderson

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=20030529052922.GA4324@ccpu.com \
    --to=andy@ccpu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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.