public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Walberg <twalberg@mindspring.com>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: nfs is stupid ("getfh failed")
Date: Fri, 7 Sep 2001 09:17:16 -0500	[thread overview]
Message-ID: <20010907091716.A15494@mindspring.com> (raw)
In-Reply-To: <002b01c136e1$3bb36a80$81d4870a@cartman> <15256.46017.7716.689482@notabene.cse.unsw.edu.au> <000c01c1379c$c427c0d0$81d4870a@cartman>
In-Reply-To: <000c01c1379c$c427c0d0$81d4870a@cartman> from Michael Rothwell on 09/07/2001 07:58

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

On 09/07/2001 08:58 -0400, Michael Rothwell wrote:
>>	From: "Neil Brown" <neilb@cse.unsw.edu.au>
>>	
>>	> This is not allowed, and makes no sense.
>>	
>>	It apparently is (or was, anyway) allowed, because it worked until the
>>	server was rebooted. Fluke?
>>	Are you saying that, if I export "/export", I can mount "/export/home" from
>>	a client machine? That's nice.
>>	

Yes. At least that's how Solaris, Irix, HP/UX, and several others do it. The
general rule is something along the lines of "if /a is exported, anything that
is a subdirectory of /a is accessible via NFS, so long as it is on the same
device (partition - actually major/minor pair)". So, if /export/home in your
case lives in the same file system as /export, it is accessible via NFS
as well. Now if /export/home is it's own mount point (i.e. a separate file
system), then it needs to be exported explicitly.

>>	> Simply remove the second line and your problems should go away.
>>	
>>	Thanks. I actually switched to two explicit exports; /export/files and
>>	/export/home, which works.
>>	

This works as well, with the caveat that you cannot then mount /export itself
on client machines.

				tw

-- 
twalberg@mindspring.com

[-- Attachment #2: Type: application/pgp-signature, Size: 175 bytes --]

  reply	other threads:[~2001-09-07 14:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 14:35 nfs is stupid ("getfh failed") Michael Rothwell
2001-09-07  1:59 ` Jamie Lokier
2001-09-11  7:06   ` Neil Brown
2001-09-11  9:55     ` Jamie Lokier
2001-09-11 10:01       ` Neil Brown
2001-09-07 11:47 ` Neil Brown
2001-09-07 12:58   ` Michael Rothwell
2001-09-07 14:17     ` Tim Walberg [this message]
2001-09-08  0:02     ` Johan Kullstam
2001-09-08 13:38       ` Alan Cox
2001-09-09 10:05         ` Henning P. Schmiedehausen
2001-09-09 16:44           ` Michael Rothwell
2001-09-10  6:55     ` Neil Brown
2001-09-10  9:32       ` Marcus Sundberg
2001-09-11  7:07         ` Neil Brown
2001-09-12 10:44           ` Marcus Sundberg
2001-09-12 11:13             ` Trond Myklebust
2001-09-12 12:22             ` Neil Brown

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=20010907091716.A15494@mindspring.com \
    --to=twalberg@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=rothwell@holly-springs.nc.us \
    /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