From: Pavel Machek <pavel@suse.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: recursive exports && linux nfs
Date: Sun, 17 Dec 2000 23:11:07 +0100 [thread overview]
Message-ID: <20001217231107.C474@bug.ucw.cz> (raw)
In-Reply-To: <20001212103652.A13501@cerebro.laendle> <20001215235446.H9506@bug.ucw.cz> <20001217104242.B9034@fuji.laendle>
In-Reply-To: <20001217104242.B9034@fuji.laendle>; from Marc Lehmann on Sun, Dec 17, 2000 at 10:42:42AM +0100
Hi!
> > > 2) using: I can do cd /nfs/fs, but the directoy is always empty, and when I
> > > try to step into a subdirectory I always get "No such file or directory".
> > >
> > > Thanks a lot for any insights, even if this means "this is not supported"
> > > ;)
> >
> > This can't be supported, afaict, because nfs handles have limited
> > size.
>
> Ehrm, did you really read my mail? Most people told me something like
> "recursive exports are not supported" (actually, they are and they work),
> and it seems nobody really read what I wrote :(
They do not work too well. They break guarantee that handles are
persistent across reboots. Recursive exports are huge kludge. They
have to be.
[Sorry, I did not read your mail too carefully]
> My problem is that autofs doesn't work. Example:
>
> / reiserfs
> /fs autofs
> /fs/big ext2
>
> When I exportfs /, /fs AND /fs/big then I can mount /fs on another box,
> but it is always empty, even if something (e.g. /fs/big) is mounted and
> can be accessed fine the whole time. Automounting doesn't work, either, of
> course.
>
> Another (less grave) problem is that exportfs (and/or rpc.nfsd) require
> network access and access to the volume, so they a) mount all automounted
> directories (VERY expensive) and require network access (making all
> clients NOT survive a reboot).
>
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-17 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 9:36 recursive exports && linux nfs Marc Lehmann
2000-12-15 22:54 ` Pavel Machek
2000-12-17 9:42 ` Marc Lehmann
2000-12-17 22:11 ` Pavel Machek [this message]
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=20001217231107.C474@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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.