...
After logging in to the virtual machine that you want to access the EUMETSAT data, all you need is to do is mount the NFS drive that rests on 198.18.255.1133 onto the directory where you want it. You will need sudo permissions or root access to accomplish the major steps here.
Verify access to the NFS server
You can see all exported file systems on the EUMETSAT NFS server without mounting it using the showmount command like in the example below:
Code Block language bash karatosun@myfirstvm ~$ showmount --exports 198.18.255.1133 Export list for 198.18.255.1133: ... (lot of text, but should include) /ifs/data/EUMETSAT_DATA /ifs/data/EUMETCAST ...
Info If you receive an error (e.g. timeout), please refer to the troubleshooting section below.
Create the (empty) directory where you'll mount the NFS share
You can place this anywhere you wish; we have chosen /eumetsatdata in the example here
Code Block language bash karatosun@myfirstvm ~$ sudo mkdir /eumetsatdata karatosun@myfirstvm ~$ sudo echo "run sudo mount -a" > /eumetsatdata/NFS_NOT_MOUNTED # put a placeholder file in the directory to make it clear what's (not) happened karatosun@myfirstvm ~$ sudo chmod a+rX,go-w /eumetsatdata # minimise write permissions to prevent mistakes if the mount isn't there
Info The last two commands add a little extra safety for the case that the directory is unexpectedly not mounted Mount NFS drive to the mount point
This command will do a once-off mount. If it works, you may wish to make it permanent as described in step 4
Code Block language bash karatosun@myfirstvm ~$ sudo mount 198.18.255.1133:/ifs/data/EUMETSAT_DATA /eumetsatdata
Info If you receive an error (e.g. timeout), please refer to the troubleshooting section below. If step 3 worked, you can now navigate to the /eumetsatdata directory and list all the available data with the ls -lah command
Code Block language bash [karatosun@myfirstvm ~]$ cd /eumetsatdata/ [karatosun@myfirstvm eumetsatdata]$ ls -lah total 192K drwxrwxrwx. 7 nobody nobody 124 May 26 13:00 . dr-xr-xr-x. 19 root root 260 Jul 6 13:00 .. drwxrwsr-x. 5 1002 1002 101 Nov 7 2018 eumetcast drwxr-xr-x. 3 nobody nobody 24 Apr 23 2018 mviri drwxr-xr-x. 4 nobody nobody 52 May 28 17:26 seviri
Info Note that the ownerships and permissions will generally be "nobody" Making the NFS mount permanent and persistent across reboots (optional)
Edit /etc/fstab file of the VM with your editor of choice
Code Block language bash karatosun@myfirstvm ~$ sudo nano /etc/fstab
and add the following line
Code Block language bash 198.18.255.1133:/ifs/data/EUMETSAT_DATA /eumetsatdata nfs defaults 0 0
A complete example of a /etc/fstab can be seen in the block below (do not copy all of this!)
Code Block language bash collapse true # /etc/fstab # Created by anaconda on Thu Aug 8 12:37:33 2019 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=3ef2b806-efd7-4eef-aaa2 / xfs defaults 0 0 # mount the EUMETSAT NFS server to /eumetsatdata 198.18.255.11:/ifs/data/EUMETSAT_DATA /eumetsatdata nfs defaults 0 0
To test the persistent configuration, unmount the share, then try to automatically remount it:
Code Block language bash karatosun@myfirstvm ~$ sudo umount /eumetsatdata karatosun@myfirstvm ~$ sudo mount -a
Info If you see an error and the manual mount worked previously, please check for typos!
...
Timeout/network connectivity: test that you can ping the NFS server with ping 198.18.255.11 33 command. If not, you have a routing, firewalling or security group issue. Assuming a default setup, the most likely issue is a security group problem. Until we provide a knowledgebase knowledge base article, please contact us.
...