doc-exports/docs/sfs/umn/sfs_01_0057.html

<a name="sfs_01_0057"></a><a name="sfs_01_0057"></a>

<h1 class="topictitle1">Mounting a File System Fails</h1>
<div id="body1474254982340"><div class="section" id="sfs_01_0057__section10868397112233"><h4 class="sectiontitle">Symptom</h4><p id="sfs_01_0057__p26504972112244">When running the <strong id="sfs_01_0057__b247764321118">mount</strong> command to mount the file system to the ECSs, the message <span class="wintitle" id="sfs_01_0057__wintitle1071506395105924"><b>access denied</b></span> is displayed.</p>
</div>
<div class="section" id="sfs_01_0057__section484814811237"><h4 class="sectiontitle">Possible Causes</h4><ul id="sfs_01_0057__ul2026311811154"><li id="sfs_01_0057__li5870543311154">Cause 1: The file system has been deleted.</li><li id="sfs_01_0057__li2620400911154">Cause 2: The ECS on which the <strong id="sfs_01_0057__b189129101214">mount</strong> command is executed and the mounted file system are not in the same VPC.</li><li id="sfs_01_0057__li5586888311154">Cause 3: The mount point in the <strong id="sfs_01_0057__b842352706185626">mount</strong> command is incorrect.</li><li id="sfs_01_0057__li1947131517910">Cause 4: The IP address used for accessing SFS is a virtual IP address.</li><li id="sfs_01_0057__li1367192817421">Cause 5: The DNS used for accessing the file system is incorrect.</li></ul>
</div>
<div class="section" id="sfs_01_0057__section3353356112331"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="sfs_01_0057__p31354664112659">Take troubleshooting measures based on possible causes.</p>
</div>
<div class="section" id="sfs_01_0057__section5391128112350"><h4 class="sectiontitle">Solution</h4><ul id="sfs_01_0057__ul8096460112759"><li id="sfs_01_0057__li5964401811323">Cause 1: The file system has been deleted.<div class="p" id="sfs_01_0057__p13950651113658"><a name="sfs_01_0057__li5964401811323"></a><a name="li5964401811323"></a>Log in to the management console and check whether the file system has been deleted.<ul id="sfs_01_0057__ul52612488113215"><li id="sfs_01_0057__li3750351113215">If yes, create a file system or select an existing file system to mount. The ECS to which the file system is to be mounted must reside in the same VPC as the mounted file system.</li><li id="sfs_01_0057__li33753160113215">If no, go to Cause 2.</li></ul>
</div>
</li><li id="sfs_01_0057__li8003624112759">Cause 2: The ECS on which the <strong id="sfs_01_0057__b7341419131216">mount</strong> command is executed and the mounted file system are not in the same VPC.<div class="p" id="sfs_01_0057__p36473394112812">Log in to the management console and check whether the ECS and the file system belong to the same VPC.<ul id="sfs_01_0057__ul63280071112759"><li id="sfs_01_0057__li4923757112759">If yes, go to Cause 3.</li><li id="sfs_01_0057__li44313821112759">If no, re-select the file system of the same VPC as the ECS.</li></ul>
</div>
</li><li id="sfs_01_0057__li1103323712034">Cause 3: The mount point in the <strong id="sfs_01_0057__b145181813112611">mount</strong> command is incorrect.<ol id="sfs_01_0057__ol4120860714953"><li id="sfs_01_0057__li1895172814953">Log in to the management console and check whether the mount point is the same as the one in the <strong id="sfs_01_0057__b8423527061940">mount</strong> command.</li><li id="sfs_01_0057__li3853534914103">If the mount point in the <strong id="sfs_01_0057__b84235270619457">mount</strong> command is incorrectly entered, correct it and run the command again.</li></ol>
</li><li id="sfs_01_0057__li860018510307">Cause 4: The IP address used for accessing SFS is a virtual IP address.<p id="sfs_01_0057__p1045143023916"><a name="sfs_01_0057__li860018510307"></a><a name="li860018510307"></a>Log in to the ECS, run the <strong id="sfs_01_0057__b136661521164518">ping</strong> command and use the IP address of the ECS to access SFS. Check whether the service is reachable. See <a href="#sfs_01_0057__fig1289720753914">Figure 1</a>.</p>
<ul id="sfs_01_0057__ul176231633133916"><li id="sfs_01_0057__li9623103319397">If yes, the network problem has been resolved. Check other possible causes.</li><li id="sfs_01_0057__li87481916114016">If no, the ECS virtual IP address is unable to access SFS due to the network problem. Use the private IP address and run the <strong id="sfs_01_0057__b842352706111329">ping</strong> command to access SFS and check whether the service is reachable.<div class="fignone" id="sfs_01_0057__fig1289720753914"><a name="sfs_01_0057__fig1289720753914"></a><a name="fig1289720753914"></a><span class="figcap"><b>Figure 1 </b>Running the ping command to access SFS</span><br><span><img id="sfs_01_0057__image178979753913" src="en-us_image_0113980196.png" title="Click to enlarge" class="imgResize"></span></div>
</li></ul>
</li><li id="sfs_01_0057__li1787863416127">Cause 5: The DNS used for accessing the file system is incorrect.<p id="sfs_01_0057__p8167122911484"><a name="sfs_01_0057__li1787863416127"></a><a name="li1787863416127"></a>Run the following command to check whether the DNS is correct:</p>
<p id="sfs_01_0057__p8421726144816"><strong id="sfs_01_0057__b0555941119">nslookup </strong><i><span class="varname" id="sfs_01_0057__varname13596931120">File system domain name</span></i></p>
<p id="sfs_01_0057__p03581245174920">Check whether the resolved IP address is in segment <strong id="sfs_01_0057__b842352706111916">100</strong>.</p>
<ul id="sfs_01_0057__ul1381920268132"><li id="sfs_01_0057__li173742510131">If yes, the DNS configuration is correct. Check other possible causes.</li><li id="sfs_01_0057__li14165156184413">If no, the DNS configuration is incorrect. Reconfigure DNS by referring to <a href="sfs_01_0038.html">Configuring DNS</a>.</li></ul>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0056.html">Troubleshooting</a></div>
</div>
</div>


<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>