We come to the last section about troubleshooting and the last storage service that we are looking at is about file storage service. File storage service as we have seen earlier is accessed using a Mount Target which gives you a network end point within the VCN through which you connect and work. When you work with file storage, you might have some specific issues. Number one, have you created a file system and an appropriate Mount Target to expose the export of the file system? That is something to be created and the file system and Mount Target should be connected with at least the mount options for it from the file system page. For example, if I go to my File Systems page, I should see that the file system of interest is all ready created. And if I click on the file system I should see at least one export given from a given Mount Target. Obviously when you create additional exports, you can expose it with multiple Mount Targets. Then, when you want to mount a file system, there are specific things to be taken care. Number one, there is the need that the security list should have the corresponding ingress rules created and you need to have the NFS client installed in the compute instance, and a directory created to which you mount the Mount Target. All these have to be taken care. So you need to have the correct client installed, you need to have the Mount Target in a sub net provision which has the correct networking security rules. For example, in my environment that I have created, if I go to the Mount Target page, I will see it is provisioned in a particular subnet which is a private subnet. And if I go to that sub net, that submit should have ingress rules configured in such a way. If I go to my private subnets, the private subnets has a particular security list. It should have ingress rules configured to allow the communicate required. These are the port protocols that should be enabled, TCP and UDP specific ports and the network cider from where incoming requests will be allowed. In this example I have given the entire VC Insider. If you are using from any other VCN you should have implemented VCN peering and allowed those to be also allowed. Of course if you're using VCN peering or compromised connectivity, you should have had the route table also configured appropriately along with the firewall rules. To access the file system after checking the rules, you need to have the right client software installed and a amount point created for mounting the file system. And finally did your mount command execute can be found with this find mount command to identify whether it is done. In my example of my implementation that I have, I have logged into a computer instance, and if I do a DF I see nothing is there because my mount is not yet initialized for this file system. So, because I have done a reboot of the compute instance, it is not auto mounted. If you want an auto amount to happen, you need to have an FS tab entry. In this case I'm going to rerun my mount command and the idea here is the client is all ready installed. The directory is also all ready there. If I go and look into cd/mnt, I see that the directory is available. Right now if I go into this directory and look into the contents, nothing is there because I have not mounted it. I can just copy this command and run it, and as a result of this, the amount should have happened. And if I now go to my directory, I will see the contents within the file system. And as shown in the command in the slide, if I do a find mount command, it should tell me that this mount is, or this directory is used to mount this particular file system and the privileges that are given. We see that it is an NFS based amount that is given as part of the output. So this is how you should validate whether your file system is accessible by looking at all the options required to use file systems from compute instances.
