From: Pavel Machek <pavel@suse.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: recursive exports && linux nfs
Date: Fri, 15 Dec 2000 23:54:46 +0100 [thread overview]
Message-ID: <20001215235446.H9506@bug.ucw.cz> (raw)
In-Reply-To: <20001212103652.A13501@cerebro.laendle>
In-Reply-To: <20001212103652.A13501@cerebro.laendle>; from Marc Lehmann on Tue, Dec 12, 2000 at 10:36:53AM +0100
Hi!
> I am trying to export the whole filesystem hierarchy on one of my servers
> (this includes /fs, which is an automounted directory using autofs).
>
> Now I have two problems:
>
> 1) exporting: exportfs does not really exports filesystems that are
> not present when exportfs is being called (some of my filesystems
> are only available temporarily). Also, exportfs of course forces the mount
> of all filesystems that are mountable, which can take considerable time.
>
> 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".
>
> I am using linux-2.2.18, nfsv3 + nfs-utils-0.2.1.
>
> 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.
Pavel
--
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/
next prev parent reply other threads:[~2000-12-16 22:23 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 [this message]
2000-12-17 9:42 ` Marc Lehmann
2000-12-17 22:11 ` Pavel Machek
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=20001215235446.H9506@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.