From: devzero@web.de
To: NFS@lists.sourceforge.net
Subject: nfs exports & bind mounts
Date: Sat, 10 Nov 2007 22:36:45 +0100 [thread overview]
Message-ID: <2077779951@web.de> (raw)
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 has the same size as file after successful bind-mount
i can loopback-mount /otherpath/dummyfile to /otherpath/mnt if file/dummyfile 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 ?
regards
roland
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
-------------------------------------------------------------------------
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 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 21:36 devzero [this message]
2007-11-10 22:29 ` nfs exports & bind mounts Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 22:39 devzero
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=2077779951@web.de \
--to=devzero@web.de \
--cc=NFS@lists.sourceforge.net \
/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.