I thought it was just another NFS request. Well, technically, it is. What I meant was another mount, and there it goes. But, I was wrong [again]! Just like the other aspect of my life. Hmm, forget it!
Ok. Let's check on the request.
Request: Mount /var/opt/edis/idocs/directory1 to server2 from box1.
Simple? May be.
Steps:
1. Entry was added to exports
2. run `exportfs -a` but error was generated:
parent directory already exported
Several attempts [solution] were tried but none succeeded.
1. comment the parent directory
2. manually exporting the child directory
Ok. Let's check on the request.
Request: Mount /var/opt/edis/idocs/directory1 to server2 from box1.
Simple? May be.
Steps:
1. Entry was added to exports
2. run `exportfs -a` but error was generated:
parent directory already exported
Several attempts [solution] were tried but none succeeded.
1. comment the parent directory
2. manually exporting the child directory
Login to the client side. Made a copy of the fstab [a great practice, just in case a stupid me does a stupid thing]. Then add it as:
# cp -p /etc/fstab /etc/fstab.backup.`date`
# vi /etc/fstab
...
/var/opt/edis/idocs/directory1 /var/opt/edis/idocs/directory1 nfs rw ...
...
~
~
The entry added for the client was specific. It means, although the "whole" parent directory was exported, I think it is possible to just put the specific directory to be accessed. At least for this case. I think, no! I need to review more about NFS. Adios!
No comments:
Post a Comment