On 3/20/25 01:43, to...@tuxteam.de wrote:
On Thu, Mar 20, 2025 at 01:29:39AM -0400, Eben King wrote:
On 3/19/25 16:19, to...@tuxteam.de wrote:
On Wed, Mar 19, 2025 at 02:53:51PM -0400, Eben King wrote:
I have this machine "alexandria". It mounts a directory from the nas
via NFS. When I export a parent directory on alexandria, the mount
point appears empty, even though you can ssh to it and see everything
there that should be. How do I get it to share the contents of that mount?
It is possible, see the file /etc/exports and its man page exports(7),
specifically the options nohide and crossmnt there.
Great to hear. I don't suppose you know how to access /etc/exports on a
WD Mycloud Mirror? Theoretically it supports SSH but I haven't got it
to work yet.
I don't even know what a WD Mycloud Mirror is :)
A two-disk NAS. Probably a pretty old one as it's been EOLed by the
manufacturer. But hey, it works for me.
This is the intermediate box which you'd like to re-export the mounted
file system?
Right. NAS:/nfs/Movies is mounted on alexandria by NFS as
/files/movies. Alex exports /files by NFS. My computer mounts
alexandria:/files and sees /files/movies/ as empty.
There are caveats, though (e.g. you might get duplicate inode numbers
from the two file systems), described in the above man page.
hmm, I'll have to see if that's a problem. So the same inode number on
two different filesystems conflict? Or what do you mean?
The man page isn't very clear, but I guess that NFS passes the inodes
along and the client uses them for file identification (cache, what
have you) and gets confused when the server's and the server's server
inodes collide. But that's only a guess.
OK, thanks.
