The officially official Devuan Forum!

Duke Nukem

Member

Registered: 2018-11-07

Posts: 59  

[SOLVED] Seeing Partitions on a Server

I have a server at 192.168.1.6 with more than one disk drive and some of those with more than one partition, for example a data partition on the mount point /home/server_name/Data/

My client PC successfully mounts (eg on /mnt by nfs) 192.168.1.6:/home/server_name and I can see the directory called Data, but it displays empty. The strange thing is that I have tried this several times, including mounting the server partition within the server either before or after the network mount, and sometimes I can see the files in the mounted partition below Data and sometimes I can't. There seems to be no consistency, and all the advice I can find seems to assume that the server only needs to show the client one level of partition.

What am I missing here? Are there some rules about this?  I suppose I could mount the server's separate partitions each as a separate entity, in parallel, rather than as a tree. That sounds a bit like Windows though.

Last edited by Duke Nukem (Yesterday 21:00:54)

steve_v

Member

Registered: 2018-01-11

Posts: 585  

Re: [SOLVED] Seeing Partitions on a Server

If you don't show us what is in /etc/exports and where your filesystems are mounted server, and /etc/fstab on the client, all that remains is speculation.
Speculation: You are trying to export a directory that contains mountpoints for other filesystems, without specifying the 'crossmnt' flag. See the exports(5) manual page.

Last edited by steve_v (Today 08:50:50)

---

Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

Duke Nukem

Member

Registered: 2018-11-07

Posts: 59  

Re: [SOLVED] Seeing Partitions on a Server

You are trying to export a directory that contains mountpoints for other filesystems, without specifying the 'crossmnt' flag.

Correct, thanks for that advice and the problem is now sorted.
FWIW, the exports manual page is not available on the client where I had been looking for it, only on the server. That's logical I suppose.