forked from docs/doc-exports
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
45 lines
6.9 KiB
HTML
45 lines
6.9 KiB
HTML
<a name="cce_faq_00200"></a><a name="cce_faq_00200"></a>
|
|
|
|
<h1 class="topictitle1">What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?</h1>
|
|
<div id="body1570791416899"><div class="section" id="cce_faq_00200__section4462133771810"><h4 class="sectiontitle">Troubleshooting Process</h4><p id="cce_faq_00200__p17987205213470">The issues here are described in order of how likely they are to occur.</p>
|
|
<p id="cce_faq_00200__p997211345215">Check these causes one by one until you find the cause of the fault.</p>
|
|
<ul id="cce_faq_00200__ul8490384195"><li id="cce_faq_00200__li34912383192"><a href="#cce_faq_00200__section239014414225">Check Item 1: Whether EVS Volumes Are Mounted Across AZs</a></li><li id="cce_faq_00200__li10595164516190"><a href="#cce_faq_00200__section15311186248">Check Item 2: Whether Multiple Permission Configurations Exist in the Storage Volume</a></li><li id="cce_faq_00200__li13954252194011"><a href="#cce_faq_00200__section151615354218">Check Item 3: Whether There Is More Than One Replica for a Deployment with EVS Volumes</a></li><li id="cce_faq_00200__li117730910589"><a href="#cce_faq_00200__section0802134413523">Check Item 4: Whether the EVS Disk File System Is Damaged</a></li></ul>
|
|
<div class="fignone" id="cce_faq_00200__fig172996113218"><span class="figcap"><b>Figure 1 </b>Troubleshooting for storage volume mounting failure or mounting timeout</span><br><span><img id="cce_faq_00200__image353311985114" src="en-us_image_0000001851585136.png"></span></div>
|
|
</div>
|
|
<div class="section" id="cce_faq_00200__section239014414225"><a name="cce_faq_00200__section239014414225"></a><a name="section239014414225"></a><h4 class="sectiontitle">Check Item 1: Whether EVS Volumes Are Mounted Across AZs</h4><p id="cce_faq_00200__p16170238204518"><strong id="cce_faq_00200__b148552595215">Symptom</strong></p>
|
|
<p id="cce_faq_00200__p27364455456">Mounting an EVS volume to a StatefulSet times out.</p>
|
|
<p id="cce_faq_00200__p1136814142710"><strong id="cce_faq_00200__b251718398311">Fault Locating</strong></p>
|
|
<p id="cce_faq_00200__p7977164517271">If your node is in <strong id="cce_faq_00200__b13634164615310">AZ 1</strong> but the volume to be mounted is in <strong id="cce_faq_00200__b763415462319">AZ 2</strong>, the mounting times out and the volume cannot be mounted.</p>
|
|
<p id="cce_faq_00200__p13565448174510"><strong id="cce_faq_00200__b1723814715228">Solution</strong></p>
|
|
<p id="cce_faq_00200__p12308124912226">Create a volume in the same AZ as the node and mount the volume.</p>
|
|
</div>
|
|
<div class="section" id="cce_faq_00200__section15311186248"><a name="cce_faq_00200__section15311186248"></a><a name="section15311186248"></a><h4 class="sectiontitle">Check Item 2: Whether Multiple Permission Configurations Exist in the Storage Volume</h4><p id="cce_faq_00200__p73051222152610">If the volume to be mounted stores too many data and involves permission-related configurations, the file permissions need to be modified one by one, which results in mounting timeout.</p>
|
|
<p id="cce_faq_00200__p8305622192611"><strong id="cce_faq_00200__b1279510811416">Fault Locating</strong></p>
|
|
<ul id="cce_faq_00200__ul14558214183015"><li id="cce_faq_00200__li125586148307">Check whether the <strong id="cce_faq_00200__b141417124416">securityContext</strong> field contains <strong id="cce_faq_00200__b141831217414">runAsuser</strong> and <strong id="cce_faq_00200__b101910128416">fsGroup</strong>. <strong id="cce_faq_00200__b44071718447">securityContext</strong> is a Kubernetes field that defines the permission and access control settings of pods or containers.</li><li id="cce_faq_00200__li855817148307">Check whether the startup commands contain commands used to obtain or modify file permissions, such as <strong id="cce_faq_00200__b599324419">ls</strong>, <strong id="cce_faq_00200__b19155320413">chmod</strong>, and <strong id="cce_faq_00200__b1154321549">chown</strong>.</li></ul>
|
|
<p id="cce_faq_00200__p214535443613"><strong id="cce_faq_00200__b1610163513278">Solution</strong></p>
|
|
<p id="cce_faq_00200__p2470204845312">Determine whether to modify the settings based on your service requirements.</p>
|
|
</div>
|
|
<div class="section" id="cce_faq_00200__section151615354218"><a name="cce_faq_00200__section151615354218"></a><a name="section151615354218"></a><h4 class="sectiontitle">Check Item 3: Whether There Is More Than One Replica for a Deployment with EVS Volumes</h4><p id="cce_faq_00200__p101615314219"><strong id="cce_faq_00200__b171011724455">Symptom</strong></p>
|
|
<p id="cce_faq_00200__p14104101514">The pod fails to be created, and an event indicating that the storage fails to be added is reported.</p>
|
|
<pre class="screen" id="cce_faq_00200__screen95751857856">Multi-Attach error for volume "pvc-62a7a7d9-9dc8-42a2-8366-0f5ef9db5b60" Volume is already used by pod(s) testttt-7b774658cb-lc98h</pre>
|
|
<p id="cce_faq_00200__p154915177500"><strong id="cce_faq_00200__b1513354245118">Fault Locating</strong></p>
|
|
<p id="cce_faq_00200__p4807528161120">Check whether the number of replicas of the Deployment is greater than 1.</p>
|
|
<p id="cce_faq_00200__p16984105061012">If the Deployment uses an EVS volume, the number of replicas can only be 1. If you specify more than two pods for the Deployment on the backend, CCE does not restrict the creation of the Deployment. However, if these pods are scheduled to different nodes, some pods cannot be started because the EVS volumes used by the pods cannot be mounted to the nodes.</p>
|
|
<p id="cce_faq_00200__p121693134218"><strong id="cce_faq_00200__b7988142311571">Solution</strong></p>
|
|
<p id="cce_faq_00200__p131612318428">Set the number of replicas of the Deployment that uses an EVS volume to 1 or use other volume types.</p>
|
|
</div>
|
|
<div class="section" id="cce_faq_00200__section0802134413523"><a name="cce_faq_00200__section0802134413523"></a><a name="section0802134413523"></a><h4 class="sectiontitle">Check Item 4: Whether the EVS Disk File System Is Damaged</h4><p id="cce_faq_00200__p22611129125310"><strong id="cce_faq_00200__b153550155595">Symptom</strong></p>
|
|
<p id="cce_faq_00200__p626152905316">The pod fails to be created, and information similar to the following is displayed, indicating that the disk file system is damaged.</p>
|
|
<pre class="screen" id="cce_faq_00200__screen7261102955312">MountVolume.MountDevice failed for volume "pvc-08178474-c58c-4820-a828-14437d46ba6f" : rpc error: code = Internal desc = [09060def-afd0-11ec-9664-fa163eef47d0] /dev/sda has file system, but it is detected to be damaged</pre>
|
|
<p id="cce_faq_00200__p18262172913531"><strong id="cce_faq_00200__b10542123035917">Solution</strong></p>
|
|
<p id="cce_faq_00200__p3262182985312">Back up the disk in EVS and run the following command to restore the file system:</p>
|
|
<p id="cce_faq_00200__p1264610397558"><strong id="cce_faq_00200__b1984124814597">fsck -y {Drive letter}</strong></p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00029.html">Workload Abnormalities</a></div>
|
|
</div>
|
|
</div>
|
|
|