You are not logged in.
Pages: 1
A puzzle
_________
As a preamble, let me explain that the "problem" I have only manifests itself on the 2 PCs that I use as primary PCs in my office. I have not checked every client on my LAN, but I have checked 4 other PCs and they all perform as expected.
I was originally writing to request help, but I have found a solution, almost by accident, and I no longer need help. But the situation does puzzle me, and if anyone can explain or suggest why my normal mounting procedure does not work on the 2 primary PCs, that will solve the puzzle for me.
My workaround
_______________
I could not mount /mnt/auxilliary from the server on my 2 primary clients, but when I created /mnt/aux on the server and made a symbolic link in /mnt/aux to each directory in /mnt/auxilliary, I could indirectly view the contents of /mnt/auxilliary, by mount /mnt/aux on the clients.
On each client I created a /mnt/aux directory and mounted, using:
mount -t nfs demeter:/mnt/aux /mnt/aux
To my surprise, the clients showed the contents of /mnt/aux correctly event though /mnt/auxilliary could not be mounted and displayed properly on the client. It looks like the mount problem occurs only on the 2 primary clients.
Suggestions
______________
If anyone can suggest why
mount -t nfs demeter:/mnt/auxilliary /mnt/auxilliary
will not work on 2 specific clients, I will appreciate understanding why. I'm sure I have done something different on these PCs -- but what??
Jim A.
____________________________________________
Below here is my original request for help.
No need to read below unless you are trying
to figure out my "puzzle".
____________________________________________
I am having trouble mounting a file system that is available on a server named "demeter". All of the PCs are running the boron release:
% lsb_release -a
No LSB modules are available.
Distributor ID: Bunsenlabs
Description: BunsenLabs GNU/Linux 12 (Boron)
Release: 12
Codename: boron
Here is a diagram of my local setup:
demeter(server) snider(server)
| | |
| | |
| ________________________
| | | |
| client1 sutton client-n
|
portable
hard
drive
NOTE 1: the portable hard drive is mounted on "demeter" as "/mnt/auxilliary". The hard drive files system is of type "ext4".
NOTE 2: I have mounted /mnt/auxilliary on snider using
mount -t nfs demeter:/mnt/auxilliary /mnt/auxilliary
This works fine.
PROBLEM: When I try to mount /mnt/auxilliary on "sutton' or other clients on the LAN, I used the same mount command:
mount -t nfs demeter:/mnt/auxilliary /mnt/auxilliary
When I run:
ls /mnt/auxilliary
The response is empty, i.e. I cannot see the contacts of the mount directory.
NOTE 3: When I run journalctl on one of the clients, I do not see any error messages that indicate a problem with the mount command.
NOTE 4: On demeter, as root, I have run:
% exportfs -va
exporting 192.168.1.0/24:/mnt/jjaLibrary2
exporting 192.168.1.0/24:/mnt/auxilliary
exporting 192.168.1.0/24:/
where each of the PC's has an IP address on the LAN, e.g. demeter is 192.168.1.217
I am doing everything that I normally would do on older releases of bunsenlabs. Does anyone have a suggestion on what I should look at next to get mounting to work on my other PC's?
Offline
Pages: 1