Re: nfs is stupid ("getfh failed")

[Tim Walberg]

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 09/07/2001 08:58 -0400, Michael Rothwell wrote:
>>	From: "Neil Brown" <[e-mail]>
>>=09
>>	> This is not allowed, and makes no sense.
>>=09
>>	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" f=
rom
>>	a client machine? That's nice.
>>=09

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 t=
hat
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.
>>=09
>>	Thanks. I actually switched to two explicit exports; /export/files and
>>	/export/home, which works.
>>=09

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

				tw

--=20
[e-mail]

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.1i

iQA/AwUBO5jW68PlnI9tqyVmEQJ4JACg4i6YPMVzX+Osk6Ux3K+PErFIu9oAnjsW
p4exFfRqLseFqynBtt8FSTTZ
=g35d
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--