public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: "David D. Hagood" <David.Hagood@ifrsys.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Automount FS re-exported via NFS fails
Date: Tue, 13 Nov 2001 18:19:39 +0000	[thread overview]
Message-ID: <01111318193900.00801@nemo> (raw)
In-Reply-To: <3BF0343C.2080409@ifrsys.com>
In-Reply-To: <3BF0343C.2080409@ifrsys.com>

On Monday 12 November 2001 20:42, David D. Hagood wrote:
> I have a situation where I have a set of file systems that are automounted
> by the automount file system in 2.4.x under /misc. I'd like to make those
> file systems available via NFS from machine.
>
> In the ideal case, I would have something like this in /etc/exports:
> /misc 10.0.0.0/255.0.0.0 (rw)
>
> Thus, a client machine could mount server:/misc as /somedir, and then cause
> a filesystem to be mounted by accessing /somedir/some_auto_filesystem.
>
> However, that doesn't work, as the NFSD seems to want to do a getfh() IOCTL
> on the auto file system, and autofs doesn't seem to support that IOCTL.

NFS don't see mountpoints. It's a strange feature but it is really done that
way. I can mount my /dev/hdc on a non-empty dir in NFS exported tree and
I see hdc filesystem when browsing it locally, but NFS clients
still see old dir contents - they don't see mounted drive there!

I don't know whether it's bug or a feature.

Every automounted dir under automount mountpoint is a mountpoint too,
that's why you can't export them via NFS.
--
vda

  reply	other threads:[~2001-11-13 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 20:42 Automount FS re-exported via NFS fails David D. Hagood
2001-11-13 18:19 ` vda [this message]
2001-11-13 16:47   ` Trond Myklebust

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=01111318193900.00801@nemo \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=David.Hagood@ifrsys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox