linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Pascal.Dupuis-s1sOSHjJPfVpcTqYljSg7g@public.gmane.org,
	nfs@lists.sourceforge.net, Jeff Layton <jlayton@redhat.com>
Subject: Re: [NFS] troubles with nohide -- crossmnt
Date: Thu, 7 Feb 2008 17:52:56 -0500	[thread overview]
Message-ID: <20080207225256.GC25374@fieldses.org> (raw)
In-Reply-To: <47AB885C.9080708-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>

On Thu, Feb 07, 2008 at 05:38:20PM -0500, Steve Dickson wrote:
> 
> 
> Pascal A. Dupuis wrote:
> > On Thu, Feb 07, 2008 at 04:41:10PM -0500, Jeff Layton wrote:
> > 
> >>> /home/user/archive	192.168.1.10(rw,subtree_check,fsid=0) 
> >>> /home/user           	192.168.1.10(rw,subtree_check,fsid=0,crossmnt) 
> >>>
> >> You shouldn't have 2 exports with the same fsid= option. They
> >> should be different. I'd suggest giving /home/user fsid=0
> >> and /home/user/archive fsid=1 (or something else).
> >>
> > 
> > OK. It made the trick. I didn't notice that both exported FS had the
> > same fsid. Thanks. Maybe this should be included in the FAQS ?
> We are working on changing things so the fsid=0 is not needed...

More helpful than a FAQ entry might just be a warning from exportfs or
mountd or whatever--it shouldn't be hard to check for the above.

I've added this to the list at:

	http://wiki.linux-nfs.org/wiki/index.php/To_do

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  parent reply	other threads:[~2008-02-07 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 21:36 [NFS] troubles with nohide -- crossmnt Pascal A. Dupuis
     [not found] ` <20080207213605.GB3034-hcDgGtZH8xNAfugRpC6u6w@public.gmane.org>
2008-02-07 21:41   ` Jeff Layton
     [not found]     ` <20080207164110.374a5ab0-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-02-07 21:52       ` Pascal A. Dupuis
     [not found]         ` <20080207215251.GC3034-hcDgGtZH8xNAfugRpC6u6w@public.gmane.org>
2008-02-07 22:38           ` Steve Dickson
     [not found]             ` <47AB885C.9080708-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-02-07 22:52               ` J. Bruce Fields [this message]
2008-02-07 23:13                 ` Trond Myklebust
     [not found]                   ` <1202426008.18376.19.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-07 23:20                     ` J. Bruce Fields

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=20080207225256.GC25374@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Pascal.Dupuis-s1sOSHjJPfVpcTqYljSg7g@public.gmane.org \
    --cc=SteveD@redhat.com \
    --cc=jlayton@redhat.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;
as well as URLs for NNTP newsgroup(s).