From: devzero@web.de
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net
Subject: Re: nfs exports & bind mounts
Date: Sat, 10 Nov 2007 23:39:54 +0100 [thread overview]
Message-ID: <2077851898@web.de> (raw)
ok, that explains why bind-mounting and exporting directories works, but no=
t files.
thanks!
=
> -----Urspr=FCngliche Nachricht-----
> Von: Trond Myklebust <trond.myklebust@fys.uio.no>
> Gesendet: 10.11.07 23:26:35
> An: devzero@web.de
> CC: NFS@lists.sourceforge.net
> Betreff: Re: [NFS] nfs exports & bind mounts
> =
> =
> On Sat, 2007-11-10 at 22:36 +0100, devzero@web.de wrote:
> > Hi !
> > =
> > i think everybody knows bind mounts.
> > =
> > i can do:
> > =
> > touch /otherpath/dummyfile
> > mount -bind /path/file /otherpath/dummyfile
> > =
> > so /path/file becomes accessible via /otherpath/dummyfile - dummyfile h=
as the same size as file after successful bind-mount
> > =
> > i can loopback-mount /otherpath/dummyfile to /otherpath/mnt if file/dum=
myfile contains a filesystem
> > =
> > when i export /otherpath via nfs (crossmnt), from the client side i can=
access the contents of the filesystem inside file/dummyfile via /otherpath=
/mnt - but i cannot access the contents of dummyfile itself, i.e. the bind=
-mount seems to get lost on export.
> > =
> > can someone tell if this is expected behaviour or if this is a bug ?
> =
> The NFS client will not cross a mount point unless the target is a
> directory. That is not a bug, it is expected behaviour.
> =
> Trond
> =
> =
______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! =
Jetzt testen! http://produkte.web.de/club/?mc=3D021130
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-11-10 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 22:39 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 21:36 nfs exports & bind mounts devzero
2007-11-10 22:29 ` 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=2077851898@web.de \
--to=devzero@web.de \
--cc=NFS@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.