yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

SFS UMN 241223 Version

Browse Source 
Reviewed-by: Sabelnikov, Dmitriy <dmitriy.sabelnikov@t-systems.com>
Co-authored-by: tanweixi <tanweixi@huawei.com>
Co-committed-by: tanweixi <tanweixi@huawei.com>
This commit is contained in:
Weixi, Tan
2025-09-22 13:37:59 +00:00
committed by zuul
parent 4d9b299c10
commit f65b8dc631
38 changed files with 625 additions and 431 deletions
Download Patch File Download Diff File Expand all files Collapse all files

143
docs/sfs/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

215
docs/sfs/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

BIN
docs/sfs/umn/en-us_image_0000001964057245.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 396 B

BIN
docs/sfs/umn/en-us_image_0000002121422188.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
docs/sfs/umn/en-us_image_0000002121554746.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
docs/sfs/umn/en-us_image_0000002121579872.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.7 KiB

BIN
docs/sfs/umn/en-us_image_0000002156781101.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.2 KiB

BIN
docs/sfs/umn/en-us_image_0000002156781377.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.5 KiB

BIN
docs/sfs/umn/en-us_image_0000002156818469.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 68 KiB

BIN
docs/sfs/umn/en-us_image_0000002156819337.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.5 KiB

30
docs/sfs/umn/en-us_topic_0034428718.html
View File

@ -1,28 +1,28 @@
<a name="EN-US_TOPIC_0034428718"></a><a name="EN-US_TOPIC_0034428718"></a>
<a name="en-us_topic_0034428718"></a><a name="en-us_topic_0034428718"></a>
<h1 class="topictitle1">What Is SFS?</h1>
<div id="body1469764805159"><div class="section" id="EN-US_TOPIC_0034428718__section2059192116103"><h4 class="sectiontitle">Overview</h4><p id="EN-US_TOPIC_0034428718__p4897627821237">Scalable File Service (SFS) provides scalable, high-performance (NAS) file storage. With SFS, you can enjoy shared file access spanning multiple Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), and containers created on Cloud Container Engine (CCE). See <a href="#EN-US_TOPIC_0034428718__fig1762807410259">Figure 1</a>.</p>
<div class="fignone" id="EN-US_TOPIC_0034428718__fig1762807410259"><a name="EN-US_TOPIC_0034428718__fig1762807410259"></a><a name="fig1762807410259"></a><span class="figcap"><b>Figure 1 </b>Accessing SFS</span><br><span><img id="EN-US_TOPIC_0034428718__image99261148174814" src="en-us_image_0259710043.png" height="411.96750000000003" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0034428718__p156381134201917"></p>
<p id="EN-US_TOPIC_0034428718__p8490406145"></p>
<div class="p" id="EN-US_TOPIC_0034428718__p9856144531015">Compared with traditional file sharing storage, SFS has the following advantages:<ul id="EN-US_TOPIC_0034428718__ul6856245171013"><li id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li42363120164311">File sharing<p id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_p5170663164322"><a name="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li42363120164311"></a><a name="en-us_topic_0059757418_li42363120164311"></a>Servers in multiple availability zones (AZs) of a same region can access the same file system concurrently and share files.</p>
</li><li id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li3575400164325">Elastic scaling<p id="EN-US_TOPIC_0034428718__p6421105621437"><a name="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li3575400164325"></a><a name="en-us_topic_0059757418_li3575400164325"></a>Storage can be scaled up or down on demand to dynamically adapt to service changes without interrupting applications. You can complete resizing with a few clicks.</p>
</li><li id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li10245495164653">Superior performance<p id="EN-US_TOPIC_0034428718__p66109542214337"><a name="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li10245495164653"></a><a name="en-us_topic_0059757418_li10245495164653"></a>SFS enables file system performance to increase as capacity grows, and it delivers a high data durability to support rapid service growth.</p>
<p id="EN-US_TOPIC_0034428718__p8547884414">The backend storage system supports both HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, which eliminate single-node faults.</p>
</li><li id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li48777570165450">Seamless integration<p id="EN-US_TOPIC_0034428718__en-us_topic_0059757418_p48915676104816"><a name="EN-US_TOPIC_0034428718__en-us_topic_0059757418_li48777570165450"></a><a name="en-us_topic_0059757418_li48777570165450"></a>SFS supports Network File System (NFS). With this standard protocol, a broad range of mainstream applications can read and write data in the file system.</p>
</li><li id="EN-US_TOPIC_0034428718__li20856445181014">Easy operation<p id="EN-US_TOPIC_0034428718__p6856645161013"><a name="EN-US_TOPIC_0034428718__li20856445181014"></a><a name="li20856445181014"></a>In an intuitive graphical user interface (GUI), you can create and manage file systems with ease. </p>
<div id="body1469764805159"><div class="section" id="en-us_topic_0034428718__section2059192116103"><h4 class="sectiontitle">Overview</h4><p id="en-us_topic_0034428718__p4897627821237">Scalable File Service (SFS) provides scalable, high-performance (NAS) file storage. With SFS, you can enjoy shared file access spanning multiple Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), and containers created on Cloud Container Engine (CCE). See <a href="#en-us_topic_0034428718__fig1762807410259">Figure 1</a>.</p>
<div class="fignone" id="en-us_topic_0034428718__fig1762807410259"><a name="en-us_topic_0034428718__fig1762807410259"></a><a name="fig1762807410259"></a><span class="figcap"><b>Figure 1 </b>Accessing SFS</span><br><span><img id="en-us_topic_0034428718__image99261148174814" src="en-us_image_0259710043.png" height="411.96750000000003" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
<p id="en-us_topic_0034428718__p156381134201917"></p>
<p id="en-us_topic_0034428718__p8490406145"></p>
<div class="p" id="en-us_topic_0034428718__p9856144531015">Compared with traditional file sharing storage, SFS has the following advantages:<ul id="en-us_topic_0034428718__ul6856245171013"><li id="en-us_topic_0034428718__en-us_topic_0059757418_li42363120164311">File sharing<p id="en-us_topic_0034428718__en-us_topic_0059757418_p5170663164322"><a name="en-us_topic_0034428718__en-us_topic_0059757418_li42363120164311"></a><a name="en-us_topic_0059757418_li42363120164311"></a>Servers in multiple availability zones (AZs) of a same region can access the same file system concurrently and share files.</p>
</li><li id="en-us_topic_0034428718__en-us_topic_0059757418_li3575400164325">Elastic scaling<p id="en-us_topic_0034428718__p6421105621437"><a name="en-us_topic_0034428718__en-us_topic_0059757418_li3575400164325"></a><a name="en-us_topic_0059757418_li3575400164325"></a>Storage can be scaled up or down on demand to dynamically adapt to service changes without interrupting applications. You can complete resizing with a few clicks.</p>
</li><li id="en-us_topic_0034428718__en-us_topic_0059757418_li10245495164653">Superior performance<p id="en-us_topic_0034428718__p66109542214337"><a name="en-us_topic_0034428718__en-us_topic_0059757418_li10245495164653"></a><a name="en-us_topic_0059757418_li10245495164653"></a>SFS enables file system performance to increase as capacity grows, and it delivers a high data durability to support rapid service growth.</p>
<p id="en-us_topic_0034428718__p8547884414">The backend storage system supports both HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, which eliminate single-node faults.</p>
</li><li id="en-us_topic_0034428718__en-us_topic_0059757418_li48777570165450">Seamless integration<p id="en-us_topic_0034428718__en-us_topic_0059757418_p48915676104816"><a name="en-us_topic_0034428718__en-us_topic_0059757418_li48777570165450"></a><a name="en-us_topic_0059757418_li48777570165450"></a>SFS supports Network File System (NFS). With this standard protocol, a broad range of mainstream applications can read and write data in the file system.</p>
</li><li id="en-us_topic_0034428718__li20856445181014">Easy operation<p id="en-us_topic_0034428718__p6856645161013"><a name="en-us_topic_0034428718__li20856445181014"></a><a name="li20856445181014"></a>In an intuitive graphical user interface (GUI), you can create and manage file systems with ease. </p>
</li></ul>
</div>
</div>
<div class="section" id="EN-US_TOPIC_0034428718__section85195351870"><h4 class="sectiontitle">Accessing SFS</h4><p id="EN-US_TOPIC_0034428718__p87556854319">You can access SFS on the management console or via APIs by sending HTTPS requests.</p>
<ul id="EN-US_TOPIC_0034428718__ul147560817436"><li id="EN-US_TOPIC_0034428718__li87561681438">APIs<p id="EN-US_TOPIC_0034428718__p375613824311"><a name="EN-US_TOPIC_0034428718__li87561681438"></a><a name="li87561681438"></a>Use APIs if you need to integrate SFS into a third-party system for secondary development. For detailed operations, see <a href="https://docs.otc.t-systems.com/en-us/api/sfs/sfs_02_0001.html" target="_blank" rel="noopener noreferrer">Scalable File Service API Reference</a>.</p>
</li><li id="EN-US_TOPIC_0034428718__li1275610874315">Management console<p id="EN-US_TOPIC_0034428718__p3756118114319"><a name="EN-US_TOPIC_0034428718__li1275610874315"></a><a name="li1275610874315"></a>Use the console if you prefer a web-based UI to perform operations.</p>
<div class="section" id="en-us_topic_0034428718__section85195351870"><h4 class="sectiontitle">Accessing SFS</h4><p id="en-us_topic_0034428718__p87556854319">You can access SFS on the management console or via APIs by sending HTTPS requests.</p>
<ul id="en-us_topic_0034428718__ul147560817436"><li id="en-us_topic_0034428718__li87561681438">APIs<p id="en-us_topic_0034428718__p375613824311"><a name="en-us_topic_0034428718__li87561681438"></a><a name="li87561681438"></a>Use APIs if you need to integrate SFS into a third-party system for secondary development. For detailed operations, see <a href="https://docs.otc.t-systems.com/en-us/api/sfs/sfs_02_0001.html" target="_blank" rel="noopener noreferrer">Scalable File Service API Reference</a>.</p>
</li><li id="en-us_topic_0034428718__li1275610874315">Management console<p id="en-us_topic_0034428718__p3756118114319"><a name="en-us_topic_0034428718__li1275610874315"></a><a name="li1275610874315"></a>Use the console if you prefer a web-based UI to perform operations.</p>
</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

308
docs/sfs/umn/en-us_topic_0034428727.html
View File

File diff suppressed because it is too large Load Diff

25
docs/sfs/umn/en-us_topic_0037925065.html
View File

@ -1,25 +0,0 @@
<a name="EN-US_TOPIC_0037925065"></a><a name="EN-US_TOPIC_0037925065"></a>
<h1 class="topictitle1">Overview</h1>
<div id="body1474251606665"><p id="EN-US_TOPIC_0037925065__p153145213519">This section describes how to use SFS.</p>
<p id="EN-US_TOPIC_0037925065__p8060118">After creating a file system, you cannot directly access the file system. Instead, you need to mount the file system to ECSs.</p>
<p id="EN-US_TOPIC_0037925065__p1096525020338"><a href="#EN-US_TOPIC_0037925065__fig1830989795513">Figure 1</a> shows the process for creating and mounting an SFS Turbo file system.</p>
<p id="EN-US_TOPIC_0037925065__p87441243173410"><a href="#EN-US_TOPIC_0037925065__fig198881945142515">Figure 2</a> shows the process for creating and mounting an SFS Capacity-Oriented file system.</p>
<p id="EN-US_TOPIC_0037925065__p1764452975911"><a href="#EN-US_TOPIC_0037925065__fig22161519194012">Figure 3</a> shows the process for creating and mounting a general purpose file system.</p>
<div class="fignone" id="EN-US_TOPIC_0037925065__fig1830989795513"><a name="EN-US_TOPIC_0037925065__fig1830989795513"></a><a name="fig1830989795513"></a><span class="figcap"><b>Figure 1 </b>Process for using SFS Turbo</span><br><span><img id="EN-US_TOPIC_0037925065__image41397385149" src="en-us_image_0153440615.png" height="443.943626" width="521.36" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="EN-US_TOPIC_0037925065__fig198881945142515"><a name="EN-US_TOPIC_0037925065__fig198881945142515"></a><a name="fig198881945142515"></a><span class="figcap"><b>Figure 2 </b>Process for using SFS Capacity-Oriented</span><br><span><img id="EN-US_TOPIC_0037925065__image167373918312" src="en-us_image_0153455845.png" height="444.88500000000005" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="EN-US_TOPIC_0037925065__fig22161519194012"><a name="EN-US_TOPIC_0037925065__fig22161519194012"></a><a name="fig22161519194012"></a><span class="figcap"><b>Figure 3 </b>Process for using General Purpose File System</span><br><span><img id="EN-US_TOPIC_0037925065__image32171192402" src="en-us_image_0000002053880478.png" height="513.7125" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0107.html">Getting Started</a></div>
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

44
docs/sfs/umn/en-us_topic_0037934210.html
View File

@ -1,44 +0,0 @@
<a name="EN-US_TOPIC_0037934210"></a><a name="EN-US_TOPIC_0037934210"></a>
<h1 class="topictitle1">Mounting a File System Times Out</h1>
<div id="body1474254982340"><div class="section" id="EN-US_TOPIC_0037934210__section41158684111639"><h4 class="sectiontitle">Symptom</h4><p id="EN-US_TOPIC_0037934210__p39221336111646">When a file system is mounted to servers using the <strong id="EN-US_TOPIC_0037934210__b3930153263314">mount</strong> command, message <span class="wintitle" id="EN-US_TOPIC_0037934210__wintitle189381432143316"><b>timed out</b></span> is displayed.</p>
</div>
<div class="section" id="EN-US_TOPIC_0037934210__section31326994111720"><h4 class="sectiontitle">Possible Causes</h4><ul id="EN-US_TOPIC_0037934210__ul32705160105159"><li id="EN-US_TOPIC_0037934210__li32662001105159">Cause 1: The network status is not stable.</li><li id="EN-US_TOPIC_0037934210__li16790640105159">Cause 2: The network connection is abnormal.</li><li id="EN-US_TOPIC_0037934210__li114712524443">Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.</li><li id="EN-US_TOPIC_0037934210__li969295001614">Cause 4: The server that mounts the file system runs Ubuntu18 or later.</li></ul>
</div>
<div class="section" id="EN-US_TOPIC_0037934210__section34776262111735"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="EN-US_TOPIC_0037934210__p55755296111746">After the network fault is excluded, run the <strong id="EN-US_TOPIC_0037934210__b842352706183951">mount</strong> command again.</p>
</div>
<div class="section" id="EN-US_TOPIC_0037934210__section31191225111737"><h4 class="sectiontitle">Solution</h4><ul id="EN-US_TOPIC_0037934210__ul16468151016343"><li id="EN-US_TOPIC_0037934210__li54701410103415">Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.<p id="EN-US_TOPIC_0037934210__p19600116173519"><a name="EN-US_TOPIC_0037934210__li54701410103415"></a><a name="li54701410103415"></a>Re-mount the file system after the network issue is addressed.</p>
<ul id="EN-US_TOPIC_0037934210__ul4438729153610"><li id="EN-US_TOPIC_0037934210__li1743882910361">If the patch is uninstalled successfully, no further action is required.</li><li id="EN-US_TOPIC_0037934210__li124412292361">If the problem persists, see the solution for cause 3.</li></ul>
</li><li id="EN-US_TOPIC_0037934210__li74021740203710">Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.<ol id="EN-US_TOPIC_0037934210__ol651519415380"><li id="EN-US_TOPIC_0037934210__li399991613910">Check the DNS configuration of the tenant and run the <strong id="EN-US_TOPIC_0037934210__b92419829511747">cat /etc/resolv.conf</strong> command.<ul id="EN-US_TOPIC_0037934210__ul32101773912"><li id="EN-US_TOPIC_0037934210__li1531117143917">If the DNS has not been configured, configure it. For details about how to configure the DNS, see <a href="sfs_01_0038.html">Configuring DNS</a>.</li><li id="EN-US_TOPIC_0037934210__li44111720394">If the DNS has been configured, run the following command to check whether the DNS is correct:<p id="EN-US_TOPIC_0037934210__p20781717396"><a name="EN-US_TOPIC_0037934210__li44111720394"></a><a name="li44111720394"></a><strong id="EN-US_TOPIC_0037934210__b0555941119">nslookup </strong><i><span class="varname" id="EN-US_TOPIC_0037934210__varname13596931120">File system domain name</span></i></p>
<p id="EN-US_TOPIC_0037934210__p147217123916">If the resolved IP address is in network segment <strong id="EN-US_TOPIC_0037934210__b842352706111059">100</strong>, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to <a href="#EN-US_TOPIC_0037934210__li19881703916">2</a>.</p>
</li></ul>
</li><li id="EN-US_TOPIC_0037934210__li19881703916"><a name="EN-US_TOPIC_0037934210__li19881703916"></a><a name="li19881703916"></a>Modify the <strong id="EN-US_TOPIC_0037934210__b10377181015815">/etc/resolv.conf</strong> configuration file, configure the correct tenant DNS, and run <strong id="EN-US_TOPIC_0037934210__b1377910982">vi /etc/resolv.conf</strong> to edit the <strong id="EN-US_TOPIC_0037934210__b437717100813">/etc/resolv.conf</strong> file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.<div class="fignone" id="EN-US_TOPIC_0037934210__fig42120175393"><span class="figcap"><b>Figure 1 </b>Configuring DNS</span><br><span><img id="EN-US_TOPIC_0037934210__image0233178399" src="en-us_image_0147961692.png" width="NaN" height="NaN"></span></div>
<div class="p" id="EN-US_TOPIC_0037934210__p22406822201147">The format is as follows:<pre class="screen" id="EN-US_TOPIC_0037934210__screen1852931020934">nameserver 100.125.4.25</pre>
</div>
<ul id="EN-US_TOPIC_0037934210__ul83161743911"><li id="EN-US_TOPIC_0037934210__li43211179390">If the configuration succeeds, go to <a href="#EN-US_TOPIC_0037934210__li1340101763913">3</a>.</li><li id="EN-US_TOPIC_0037934210__li14331017163914">If the configuration fails, run the <strong id="EN-US_TOPIC_0037934210__b842352706114229">lsattr /etc/resolv.conf</strong> command. If the information shown in <a href="#EN-US_TOPIC_0037934210__fig93781793919">Figure 2</a> is displayed, the file is locked.<div class="fignone" id="EN-US_TOPIC_0037934210__fig93781793919"><a name="EN-US_TOPIC_0037934210__fig93781793919"></a><a name="fig93781793919"></a><span class="figcap"><b>Figure 2 </b>A locked file</span><br><span><img id="EN-US_TOPIC_0037934210__image63814171394" src="en-us_image_0147961696.png" width="NaN" height="NaN"></span></div>
<p id="EN-US_TOPIC_0037934210__p16391517183917">Run the <strong id="EN-US_TOPIC_0037934210__b18872536487">chattr -i/etc/resolv.conf</strong> command to unlock the file. Then, re-configure the DNS and go to <a href="#EN-US_TOPIC_0037934210__li1340101763913">3</a>.</p>
</li></ul>
</li><li id="EN-US_TOPIC_0037934210__li1340101763913"><a name="EN-US_TOPIC_0037934210__li1340101763913"></a><a name="li1340101763913"></a>Press <strong id="EN-US_TOPIC_0037934210__b51116037112652">Esc</strong>, input <strong id="EN-US_TOPIC_0037934210__b58164000112657">:wq</strong>, and press <strong id="EN-US_TOPIC_0037934210__b6357507311271">Enter</strong> to save the changes and exit the vi editor.</li><li id="EN-US_TOPIC_0037934210__li842131720393">The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See <a href="#EN-US_TOPIC_0037934210__fig155441710394">Figure 3</a> and <a href="#EN-US_TOPIC_0037934210__fig056217113912">Figure 4</a>.<div class="fignone" id="EN-US_TOPIC_0037934210__fig155441710394"><a name="EN-US_TOPIC_0037934210__fig155441710394"></a><a name="fig155441710394"></a><span class="figcap"><b>Figure 3 </b>VPC details</span><br><span><img id="EN-US_TOPIC_0037934210__image0604174845710" src="en-us_image_0147961699.png" height="154.28" width="465.5" title="Click to enlarge" class="imgResize"></span></div>
<p id="EN-US_TOPIC_0037934210__p1049405121818"></p>
<div class="fignone" id="EN-US_TOPIC_0037934210__fig056217113912"><a name="EN-US_TOPIC_0037934210__fig056217113912"></a><a name="fig056217113912"></a><span class="figcap"><b>Figure 4 </b>Modifying the DNS</span><br><span><img id="EN-US_TOPIC_0037934210__image138726493221" src="en-us_image_0147961721.png" height="369.74" width="465.5" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="EN-US_TOPIC_0037934210__li565161723918">(Optional) Restart the server.</li><li id="EN-US_TOPIC_0037934210__li7698171174518">Run the <strong id="EN-US_TOPIC_0037934210__b27341193711">mount</strong> command again.<ul id="EN-US_TOPIC_0037934210__ul1965433458"><li id="EN-US_TOPIC_0037934210__li59744384511">If the problem is solved, no further action is required.</li><li id="EN-US_TOPIC_0037934210__li310019432454">If the problem persists, see the solution for cause 4.</li></ul>
</li></ol>
</li><li id="EN-US_TOPIC_0037934210__li333611319466">Cause 4: The server that mounts the file system runs Ubuntu18 or later.<ol id="EN-US_TOPIC_0037934210__ol14992114884616"><li id="EN-US_TOPIC_0037934210__li29921148104616">Reconfigure DNS by referring to <a href="sfs_01_0038.html">Configuring DNS</a>.</li><li id="EN-US_TOPIC_0037934210__li37811357410">Check whether the target server running Ubuntu18 or later uses a private image.<ul id="EN-US_TOPIC_0037934210__ul1258391396"><li id="EN-US_TOPIC_0037934210__li5584211498">If yes, go to <a href="#EN-US_TOPIC_0037934210__li199471275217">4</a>.</li><li id="EN-US_TOPIC_0037934210__li5586711499">If no, go to <a href="#EN-US_TOPIC_0037934210__li107041047680">3</a>.</li></ul>
</li><li id="EN-US_TOPIC_0037934210__li107041047680"><a name="EN-US_TOPIC_0037934210__li107041047680"></a><a name="li107041047680"></a>Convert the public image server to a private image server.<ol type="a" id="EN-US_TOPIC_0037934210__ol11704114715811"><li id="EN-US_TOPIC_0037934210__li57046472083"><a name="EN-US_TOPIC_0037934210__li57046472083"></a><a name="li57046472083"></a>To create a private image based on an existing ECS, see section "Creating an Image" in the <em id="EN-US_TOPIC_0037934210__i1816631044">Elastic Cloud Server User Guide</em>.</li><li id="EN-US_TOPIC_0037934210__li487420128456">Use the private image created in <a href="#EN-US_TOPIC_0037934210__li57046472083">3.a</a> to create an ECS or change the ECS OS. For details, see section "Changing the OS" in the <em id="EN-US_TOPIC_0037934210__i6673536286">Elastic Cloud Server User Guide</em>.</li></ol>
</li><li id="EN-US_TOPIC_0037934210__li199471275217"><a name="EN-US_TOPIC_0037934210__li199471275217"></a><a name="li199471275217"></a>Log in to the server and mount the file system again.</li></ol>
</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>

2
docs/sfs/umn/sfs_01_0002.html
View File

@ -4,7 +4,7 @@
<div id="body1557801021081"><div class="section" id="sfs_01_0002__en-us_topic_0184026189_section388255972712"><h4 class="sectiontitle">Concept</h4><p id="sfs_01_0002__en-us_topic_0184026189_p212716216381">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
<ul id="sfs_01_0002__en-us_topic_0184026189_ul86578533460"><li id="sfs_01_0002__en-us_topic_0184026189_li14657175334618">A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="sfs_01_0002__en-us_topic_0184026189_li45875020473">An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.</li></ul>
<p id="sfs_01_0002__en-us_topic_0184026189_p1479174514614"><a href="#sfs_01_0002__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
<div class="fignone" id="sfs_01_0002__en-us_topic_0184026189_fig8747114281212"><a name="sfs_01_0002__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="sfs_01_0002__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png" width="NaN" height="NaN"></span></div>
<div class="fignone" id="sfs_01_0002__en-us_topic_0184026189_fig8747114281212"><a name="sfs_01_0002__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="sfs_01_0002__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
</div>
<div class="section" id="sfs_01_0002__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="sfs_01_0002__en-us_topic_0184026189_p68521454132212">Select a region closest to your target users for lower network latency and quick access.</p>
</div>

2
docs/sfs/umn/sfs_01_0004.html
View File

@ -20,7 +20,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0005.html
View File

@ -266,7 +266,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0006.html
View File

@ -18,7 +18,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0007.html
View File

@ -69,7 +69,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0008.html
View File

@ -11,7 +11,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0011.html
View File

@ -16,7 +16,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0013.html
View File

@ -79,7 +79,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0033386660.html">Introduction</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0163.html">Introduction</a></div>
</div>
</div>

2
docs/sfs/umn/sfs_01_0030.html
View File

@ -20,6 +20,8 @@
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0044.html">Backup</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0334.html">Managing SFS Turbo+OBS Storage Interworking</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0046.html">Monitoring</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0340.html">Auditing</a></strong><br>

2
docs/sfs/umn/sfs_01_0032.html
View File

@ -9,7 +9,7 @@
</div>
<div class="section" id="sfs_01_0032__section1016916187178"><h4 class="sectiontitle">Restrictions</h4><ul id="sfs_01_0032__ul741218591550"><li id="sfs_01_0032__li104126598554">Both system-defined policies and custom policies are supported in SFS Turbo file systems.</li></ul>
</div>
<div class="section" id="sfs_01_0032__section142281352125915"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="sfs_01_0032__fig625610403530"><a name="sfs_01_0032__fig625610403530"></a><a name="fig625610403530"></a><span class="figcap"><b>Figure 1 </b>Process for granting SFS permissions</span><br><span><img class="vsd" id="sfs_01_0032__image8257840115317" src="en-us_image_0221089836.png" width="NaN" height="NaN"></span></div>
<div class="section" id="sfs_01_0032__section142281352125915"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="sfs_01_0032__fig625610403530"><a name="sfs_01_0032__fig625610403530"></a><a name="fig625610403530"></a><span class="figcap"><b>Figure 1 </b>Process for granting SFS permissions</span><br><span><img class="vsd" id="sfs_01_0032__image8257840115317" src="en-us_image_0221089836.png"></span></div>
<ol id="sfs_01_0032__ol23988231126"><li id="sfs_01_0032__li539812235120"><a name="sfs_01_0032__li539812235120"></a><a name="li539812235120"></a>Create a user group and assign permissions to it.<p id="sfs_01_0032__p2028474791210"><a name="sfs_01_0032__li539812235120"></a><a name="li539812235120"></a>Create a user group on the IAM console, and attach the <strong id="sfs_01_0032__b19815317202">SFS Turbo ReadOnlyAccess</strong> policy to the group.</p>
</li><li id="sfs_01_0032__li214515333122">Create a user and add it to a user group.<p id="sfs_01_0032__p164319500123"><a name="sfs_01_0032__li214515333122"></a><a name="li214515333122"></a>Create a user on the IAM console and add the user to the group created in <a href="#sfs_01_0032__li539812235120">1</a>.</p>
</li><li id="sfs_01_0032__li1084136121217">Log in and verify permissions.<p id="sfs_01_0032__p865613303275"><a name="sfs_01_0032__li1084136121217"></a><a name="li1084136121217"></a>Log in to the SFS console using the created user, and verify that the user only has read permissions for SFS.</p>

4
docs/sfs/umn/sfs_01_0044.html
View File

@ -14,9 +14,9 @@
<div class="section" id="sfs_01_0044__section1629635834112"><a name="sfs_01_0044__section1629635834112"></a><a name="section1629635834112"></a><h4 class="sectiontitle">Using a Backup to Create a File System</h4><p id="sfs_01_0044__p875016544211">In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Data on the new file system is the same as that in the backup.</p>
<ol id="sfs_01_0044__ol12903165616453"><li id="sfs_01_0044__li280961232010"><span>Log in to CBR Console.</span><p><ol type="a" id="sfs_01_0044__en-us_topic_0157095234_ol6567385123151"><li id="sfs_01_0044__en-us_topic_0157095234_li5480597823151">Log in to the management console.</li><li id="sfs_01_0044__en-us_topic_0157095234_li69106284253">Click <span><img id="sfs_01_0044__en-us_topic_0157095234_image1844744225011" src="en-us_image_0000001304536416.png"></span> in the upper left corner and select your desired region and project.</li><li id="sfs_01_0044__en-us_topic_0157095234_li4225424523410">Choose <strong id="sfs_01_0044__b47301456102915">Storage</strong> &gt; <strong id="sfs_01_0044__b87411556122910">Cloud Backup and Recovery</strong> &gt; <strong id="sfs_01_0044__b12746125612913">SFS Turbo Backups</strong>.</li></ol>
</p></li><li id="sfs_01_0044__li1981231214204"><span>Click the <span class="wintitle" id="sfs_01_0044__wintitle176521813304"><b>Backups</b></span> tab and locate the desired backup.</span></li><li id="sfs_01_0044__li1913813526228"><span>If the status of the target backup is <strong id="sfs_01_0044__b14188410163312">Available</strong>, click <strong id="sfs_01_0044__b3215610143313">Create File System</strong> in the <strong id="sfs_01_0044__b5216310193317">Operation</strong> column of the backup.</span></li><li id="sfs_01_0044__li1113905272210"><span>Set the file system parameters. See <a href="#sfs_01_0044__fig126043518315">Figure 1</a>.</span><p><div class="fignone" id="sfs_01_0044__fig126043518315"><a name="sfs_01_0044__fig126043518315"></a><a name="fig126043518315"></a><span class="figcap"><b>Figure 1 </b>Create File System</span><br><span><img id="sfs_01_0044__image76044511337" src="en-us_image_0000001357615949.png" height="360.0975" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
<div class="note" id="sfs_01_0044__note940514380235"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sfs_01_0044__ul1040523852313"><li id="sfs_01_0044__li134051138162315">For detailed parameter descriptions, see table "Parameter description" under <a href="en-us_topic_0034428727.html#EN-US_TOPIC_0034428727__table724582213143">Table 3</a>.</li></ul>
<div class="note" id="sfs_01_0044__note940514380235"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sfs_01_0044__ul1040523852313"><li id="sfs_01_0044__li134051138162315">For detailed parameter descriptions, see table "Parameter description" under <a href="en-us_topic_0034428727.html#en-us_topic_0034428727__table724582213143">Table 3</a>.</li></ul>
</div></div>
</p></li><li id="sfs_01_0044__li1014513525225"><span>Click <strong id="sfs_01_0044__b251913558114">Next</strong>.</span></li><li id="sfs_01_0044__li21461652192220"><span>Go back to the file system list and check whether the file system is successfully created.</span><p><p id="sfs_01_0044__p776603815813">You will see the file system status change as follows: <strong id="sfs_01_0044__b1439221223511">Creating</strong>, <strong id="sfs_01_0044__b10401812193510">Available</strong>, <strong id="sfs_01_0044__b54011812173517">Restoring</strong>, <strong id="sfs_01_0044__b16407111213515">Available</strong>. You may not notice the <strong id="sfs_01_0044__b376211915452">Restoring</strong> status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from <strong id="sfs_01_0044__b107717910455">Creating</strong> to <strong id="sfs_01_0044__b14772496459">Available</strong>, the file system is successfully created. After the status has changed from <strong id="sfs_01_0044__b137181631114516">Restoring</strong> to <strong id="sfs_01_0044__b1772803144513">Available</strong>, backup data has been successfully restored to the created file system.</p>
</p></li><li id="sfs_01_0044__li1014513525225"><span>Click <strong id="sfs_01_0044__b251913558114">Next</strong>.</span></li><li id="sfs_01_0044__li21461652192220"><span>Go back to the file system list and check whether the file system is successfully created.</span><p><p id="sfs_01_0044__p776603815813">You will see the file system status change as follows: <strong id="sfs_01_0044__b1439221223511">Creating</strong>, <strong id="sfs_01_0044__b10401812193510">Available</strong>, <strong id="sfs_01_0044__b54011812173517">Restoring</strong>, <strong id="sfs_01_0044__b16407111213515">Available</strong>. You may not notice the <strong id="sfs_01_0044__b23441636181112">Restoring</strong> status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from <strong id="sfs_01_0044__b107717910455">Creating</strong> to <strong id="sfs_01_0044__b14772496459">Available</strong>, the file system is successfully created. After the status has changed from <strong id="sfs_01_0044__b137181631114516">Restoring</strong> to <strong id="sfs_01_0044__b1772803144513">Available</strong>, backup data has been successfully restored to the created file system.</p>
</p></li></ol>
</div>
</div>

4
docs/sfs/umn/sfs_01_0047.html
View File

@ -1,7 +1,7 @@
<a name="sfs_01_0047"></a><a name="sfs_01_0047"></a>
<h1 class="topictitle1">SFS Metrics</h1>
<div id="body1527754616437"><p id="sfs_01_0047__p1081103317332">General purpose file systems do not support monitoring. The monitoring metrics described in this section apply only to SFS Capacity-Oriented file systems.</p>
<div id="body1527754616437"><p id="sfs_01_0047__p1081103317332">General purpose file systems do not support monitoring. This section describes only the monitoring metrics of SFS Capacity-Oriented.</p>
<div class="section" id="sfs_01_0047__section48080847153328"><h4 class="sectiontitle">Function</h4><p id="sfs_01_0047__p2234533153328">This section describes metrics reported by Scalable File Service (SFS) as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics generated for SFS.</p>
</div>
<div class="section" id="sfs_01_0047__section20110798153328"><h4 class="sectiontitle">Namespace</h4><p id="sfs_01_0047__p41611573225">SYS.SFS</p>
@ -139,7 +139,7 @@
</table>
</div>
</div>
<div class="section" id="sfs_01_0047__section893454153710"><h4 class="sectiontitle">Viewing Monitoring Statistics</h4><ol id="sfs_01_0047__ol13017281194126"><li id="sfs_01_0047__li206916213217"><span>Log in to the management console.</span></li><li id="sfs_01_0047__li0815101193410"><span>Choose <strong id="sfs_01_0047__b03425319183">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0047__b13361153181813">Cloud Eye</strong> &gt; <strong id="sfs_01_0047__b173717531185">Cloud Service Monitoring</strong> &gt; <strong id="sfs_01_0047__b193716537180">Scalable File Service</strong>. In the file system list, click <strong id="sfs_01_0047__b7391853111815">View Metric</strong> in the <strong id="sfs_01_0047__b039453111813">Operation</strong> column of the desired file system.</span></li><li id="sfs_01_0047__li12540914194542"><span>View the SFS file system monitoring data by metric or monitored duration.</span><p><p id="sfs_01_0047__p53161256103012"><a href="#sfs_01_0047__fig4460418173118">Figure 1</a> shows the monitoring graphs. For more information about Cloud Eye, see the <em id="sfs_01_0047__i1446218587577">Cloud Eye User Guide</em>.</p>
<div class="section" id="sfs_01_0047__section893454153710"><h4 class="sectiontitle">Viewing Monitoring Statistics</h4><ol id="sfs_01_0047__ol13017281194126"><li id="sfs_01_0047__li206916213217"><span>Log in to the management console.</span></li><li id="sfs_01_0047__li0815101193410"><span>Choose <strong id="sfs_01_0047__b11753155310620">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0047__b13361153181813">Cloud Eye</strong> &gt; <strong id="sfs_01_0047__b173717531185">Cloud Service Monitoring</strong> &gt; <strong id="sfs_01_0047__b193716537180">Scalable File Service</strong>. In the file system list, click <strong id="sfs_01_0047__b7391853111815">View Metric</strong> in the <strong id="sfs_01_0047__b039453111813">Operation</strong> column of the desired file system.</span></li><li id="sfs_01_0047__li12540914194542"><span>View the SFS file system monitoring data by metric or monitored duration.</span><p><p id="sfs_01_0047__p53161256103012"><a href="#sfs_01_0047__fig4460418173118">Figure 1</a> shows the monitoring graphs. For more information about Cloud Eye, see the <em id="sfs_01_0047__i1446218587577">Cloud Eye User Guide</em>.</p>
<div class="fignone" id="sfs_01_0047__fig4460418173118"><a name="sfs_01_0047__fig4460418173118"></a><a name="fig4460418173118"></a><span class="figcap"><b>Figure 1 </b>Monitoring graphs</span><br><span><img id="sfs_01_0047__image197888458816" src="en-us_image_0251362180.png" width="516.705" height="131.06152500000002" title="Click to enlarge" class="imgResize"></span></div>
</p></li></ol>
</div>

4
docs/sfs/umn/sfs_01_0048.html
View File

@ -22,7 +22,7 @@
</thead>
<tbody><tr id="sfs_01_0048__row2272193812219"><td class="cellrowborder" valign="top" width="14.008599140085993%" headers="mcps1.3.3.2.2.7.1.1 "><p id="sfs_01_0048__p1267882881318">client_connections</p>
</td>
<td class="cellrowborder" valign="top" width="14.948505149485051%" headers="mcps1.3.3.2.2.7.1.2 "><p id="sfs_01_0048__p1967816281134">Client Connections</p>
<td class="cellrowborder" valign="top" width="14.948505149485051%" headers="mcps1.3.3.2.2.7.1.2 "><p id="sfs_01_0048__p1967816281134">File System Client Connections</p>
</td>
<td class="cellrowborder" valign="top" width="26.1973802619738%" headers="mcps1.3.3.2.2.7.1.3 "><p id="sfs_01_0048__p17678202861320">Number of client connections</p>
<div class="note" id="sfs_01_0048__note18574175320404"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="sfs_01_0048__p14428832418">Only active client connections are counted.</p>
@ -153,7 +153,7 @@
</table>
</div>
</div>
<div class="section" id="sfs_01_0048__section6170132094711"><h4 class="sectiontitle">Viewing Monitoring Statistics</h4><ol id="sfs_01_0048__ol13017281194126"><li id="sfs_01_0048__li206916213217"><span>Log in to the management console.</span></li><li id="sfs_01_0048__li0815101193410"><span>View the monitoring graphs using either of the following methods.</span><p><ul id="sfs_01_0048__ul1531122918412"><li id="sfs_01_0048__li23120297412">Method 1: Choose <strong id="sfs_01_0048__b177511135135510">Service List</strong> &gt; <strong id="sfs_01_0048__b57638357552">Storage</strong> &gt; <strong id="sfs_01_0048__b1676373565510">Scalable File Service</strong>. In the file system list, click <strong id="sfs_01_0048__b1670110325371">View Metric</strong> in the <strong id="sfs_01_0048__b27641835155512">Operation</strong> column of the target file system.</li><li id="sfs_01_0048__li13256144620445">Method 2: Choose <strong id="sfs_01_0048__b19412173317165">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0048__b729313181434">Cloud Eye</strong> &gt; <strong id="sfs_01_0048__b16294181819438">Cloud Service Monitoring</strong> &gt; <strong id="sfs_01_0048__b132953185436">SFS Turbo</strong>. In the file system list, click <strong id="sfs_01_0048__b1629501844310">View Metric</strong> in the <strong id="sfs_01_0048__b1829621874319">Operation</strong> column of the target file system.</li></ul>
<div class="section" id="sfs_01_0048__section6170132094711"><h4 class="sectiontitle">Viewing Monitoring Statistics</h4><ol id="sfs_01_0048__ol13017281194126"><li id="sfs_01_0048__li206916213217"><span>Log in to the management console.</span></li><li id="sfs_01_0048__li0815101193410"><span>View the monitoring graphs using either of the following methods.</span><p><ul id="sfs_01_0048__ul1531122918412"><li id="sfs_01_0048__li23120297412">Method 1: Choose <strong id="sfs_01_0048__b177511135135510">Service List</strong> &gt; <strong id="sfs_01_0048__b57638357552">Storage</strong> &gt; <strong id="sfs_01_0048__b1676373565510">Scalable File Service</strong>. In the file system list, click <strong id="sfs_01_0048__b11276053278">View Metric</strong> in the <strong id="sfs_01_0048__b27641835155512">Operation</strong> column of the target file system.</li><li id="sfs_01_0048__li13256144620445">Method 2: Choose <strong id="sfs_01_0048__b628115191987">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0048__b729313181434">Cloud Eye</strong> &gt; <strong id="sfs_01_0048__b16294181819438">Cloud Service Monitoring</strong> &gt; <strong id="sfs_01_0048__b132953185436">SFS Turbo</strong>. In the file system list, click <strong id="sfs_01_0048__b1629501844310">View Metric</strong> in the <strong id="sfs_01_0048__b1829621874319">Operation</strong> column of the desired file system.</li></ul>
</p></li><li id="sfs_01_0048__li12540914194542"><span>View the SFS Turbo file system monitoring data by metric or monitored duration.</span><p><p id="sfs_01_0048__p53161256103012">For more information about Cloud Eye, see the <em id="sfs_01_0048__i1163012228574">Cloud Eye User Guide</em>.</p>
</p></li></ol>
</div>

4
docs/sfs/umn/sfs_01_0050.html
View File

@ -95,12 +95,12 @@
</table>
</div>
</div>
<div class="section" id="sfs_01_0050__section1294519941119"><h4 class="sectiontitle">Querying Traces</h4><ol id="sfs_01_0050__ol248972071815"><li id="sfs_01_0050__li18708202561813"><span>Log in to the management console.</span></li><li id="sfs_01_0050__li1648992015181"><span>Click <span><img id="sfs_01_0050__image207513155377" height="16.9575" src="en-us_image_0113383875.jpg" width="13.965" title="Click to enlarge" class="imgResize"></span> in the upper left corner and select a region and project.</span></li><li id="sfs_01_0050__li198294084510"><span>Choose <strong id="sfs_01_0050__b16239121775817">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0050__b16983164034517">Cloud Trace Service</strong>.</span><p><p id="sfs_01_0050__p1032815426455">The <strong id="sfs_01_0050__b2754193494611">Cloud Trace Service</strong> page is displayed.</p>
<div class="section" id="sfs_01_0050__section1294519941119"><h4 class="sectiontitle">Querying Traces</h4><ol id="sfs_01_0050__ol248972071815"><li id="sfs_01_0050__li18708202561813"><span>Log in to the management console.</span></li><li id="sfs_01_0050__li1648992015181"><span>Click <span><img id="sfs_01_0050__image207513155377" height="16.9575" src="en-us_image_0113383875.jpg" width="13.965" title="Click to enlarge" class="imgResize"></span> in the upper left corner and select a region and project.</span></li><li id="sfs_01_0050__li198294084510"><span>Choose <strong id="sfs_01_0050__b1299313108179">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0050__b16983164034517">Cloud Trace Service</strong>.</span><p><p id="sfs_01_0050__p1032815426455">The <strong id="sfs_01_0050__b2754193494611">Cloud Trace Service</strong> page is displayed.</p>
</p></li><li id="sfs_01_0050__li5826173619194"><span>In the navigation pane on the left, choose <strong id="sfs_01_0050__b831142374617">Trace List</strong>.</span></li><li id="sfs_01_0050__li14851145013018"><span>On the trace list page, set <strong id="sfs_01_0050__b842352706141135">Trace Source</strong>, <strong id="sfs_01_0050__b84235270614121">Resource Type</strong>, and <strong id="sfs_01_0050__b842352706141226">Search By</strong>, and click <strong id="sfs_01_0050__b842352706141248">Query</strong> to query the specified traces.</span><p><p id="sfs_01_0050__p198511450133013">For details about other operations, see section "Querying Real-Time Traces" in the <em id="sfs_01_0050__i131182611484">Cloud Trace Service User Guide</em>.</p>
</p></li></ol>
</div>
<div class="section" id="sfs_01_0050__section198761857144117"><h4 class="sectiontitle">Disabling or Enabling a Tracker</h4><p id="sfs_01_0050__p60695182185319">This section describes how to disable an existing tracker on the CTS console. After the tracker is disabled, the system will stop recording operations, but you can still view existing operation records.</p>
<ol id="sfs_01_0050__ol10361162210433"><li id="sfs_01_0050__li12345152284318"><span>Log in to the management console.</span></li><li id="sfs_01_0050__li234518223436"><span>Click <span><img id="sfs_01_0050__image2014352113716" height="16.9575" src="en-us_image_0113383875.jpg" width="13.965" title="Click to enlarge" class="imgResize"></span> in the upper left corner and select a region and project.</span></li><li id="sfs_01_0050__li186624844511"><span>Choose <strong id="sfs_01_0050__b159011152155820">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0050__b6869104811450">Cloud Trace Service</strong>.</span><p><p id="sfs_01_0050__p1145564934511">The <strong id="sfs_01_0050__b20984175474613">Cloud Trace Service</strong> page is displayed.</p>
<ol id="sfs_01_0050__ol10361162210433"><li id="sfs_01_0050__li12345152284318"><span>Log in to the management console.</span></li><li id="sfs_01_0050__li234518223436"><span>Click <span><img id="sfs_01_0050__image2014352113716" height="16.9575" src="en-us_image_0113383875.jpg" width="13.965" title="Click to enlarge" class="imgResize"></span> in the upper left corner and select a region and project.</span></li><li id="sfs_01_0050__li186624844511"><span>Choose <strong id="sfs_01_0050__b9181113152011">Management &amp; Deployment</strong> &gt; <strong id="sfs_01_0050__b6869104811450">Cloud Trace Service</strong>.</span><p><p id="sfs_01_0050__p1145564934511">The <strong id="sfs_01_0050__b20984175474613">Cloud Trace Service</strong> page is displayed.</p>
</p></li><li id="sfs_01_0050__li1736142244313"><span>Click <strong id="sfs_01_0050__b842352706154416">Trackers</strong> in the left pane.</span></li><li id="sfs_01_0050__li736152216431"><span>Click <strong id="sfs_01_0050__b5819179814946">Disable</strong> on the right of the tracker information.</span></li><li id="sfs_01_0050__li17361192294319"><span>Click <strong id="sfs_01_0050__b163665313299">Yes</strong>.</span></li><li id="sfs_01_0050__li10361112244317"><span>After the tracker is disabled, the available operation changes from <strong id="sfs_01_0050__b53523495141017">Disable</strong> to <strong id="sfs_01_0050__b30101567141042">Enable</strong>. To enable the tracker again, click <strong id="sfs_01_0050__b1596656141114">Enable</strong> and then click <strong id="sfs_01_0050__b27185880141134">Yes</strong>. The system will start recording operations again.</span></li></ol>
</div>
</div>

2
docs/sfs/umn/sfs_01_0056.html
View File

@ -4,7 +4,7 @@
<div id="body1474254982340"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="en-us_topic_0037934210.html">Mounting a File System Times Out</a></strong><br>
<li class="ulchildlink"><strong><a href="sfs_01_0348.html">Mounting a File System Times Out</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0057.html">Mounting a File System Fails</a></strong><br>
</li>

8
docs/sfs/umn/sfs_01_0100.html
View File

@ -1,12 +1,12 @@
<a name="sfs_01_0100"></a><a name="sfs_01_0100"></a>
<h1 class="topictitle1">Mounting a File System to a Linux ECS as a Non-root User</h1>
<div id="body1550126534609"><div class="section" id="sfs_01_0100__section15512154184412"><h4 class="sectiontitle">Scenarios</h4><p id="sfs_01_0100__p1912322155117">By default, a Linux ECS allows only the <strong id="sfs_01_0100__b695718159484">root</strong> user to run the <strong id="sfs_01_0100__b202391386132">mount</strong> command to mount a file system. However, if the permissions of user <strong id="sfs_01_0100__b995119314482">root</strong> are assigned to other users, such users can also run the <strong id="sfs_01_0100__b2851151412136">mount</strong> command to mount the file system. The following describes how to mount a file system to a Linux ECS as a common user. EulerOS is used as in this example.</p>
<div id="body1550126534609"><div class="section" id="sfs_01_0100__section15512154184412"><h4 class="sectiontitle">Scenarios</h4><p id="sfs_01_0100__p1912322155117">By default, a Linux ECS allows only the <strong id="sfs_01_0100__b6821105194710">root</strong> user to use the <strong id="sfs_01_0100__b11872680471">mount</strong> command to mount file systems, but you can grant the permissions of user <strong id="sfs_01_0100__b1270791715476">root</strong> to other users. Then, such users can use the <strong id="sfs_01_0100__b650820287477">mount</strong> command to mount the file systems. The following describes how to mount a file system to a Linux ECS as a common user. EulerOS is used in this example.</p>
</div>
<div class="section" id="sfs_01_0100__section1689695774314"><h4 class="sectiontitle">Prerequisites</h4><ul id="sfs_01_0100__ul22392394151035"><li id="sfs_01_0100__li1643177211639">A non-<strong id="sfs_01_0100__b114466933413">root</strong> user has been created on the ECS.</li><li id="sfs_01_0100__li2654923983">A file system has been created and can be mounted to the ECS by the <strong id="sfs_01_0100__b4917115853319">root</strong> user.</li><li id="sfs_01_0100__li36708344151035">The mount point of the file system has been obtained.</li></ul>
<div class="section" id="sfs_01_0100__section1689695774314"><h4 class="sectiontitle">Prerequisites</h4><ul id="sfs_01_0100__ul22392394151035"><li id="sfs_01_0100__li1643177211639">A non-<strong id="sfs_01_0100__b12803471498">root</strong> user has been created on the ECS.</li><li id="sfs_01_0100__li2654923983">A file system has been created and can be mounted to the ECS as <strong id="sfs_01_0100__b1723561619499">root</strong>.</li><li id="sfs_01_0100__li36708344151035">The mount point of the file system has been obtained.</li></ul>
</div>
<div class="section" id="sfs_01_0100__section72201550134310"><h4 class="sectiontitle">Procedure</h4><ol id="sfs_01_0100__ol342917472027"><li id="sfs_01_0100__li64303476214"><span>Log in to the ECS as user <strong id="sfs_01_0100__b825913931614">root</strong>.</span></li><li id="sfs_01_0100__li8653182515501"><span>Assign the permissions of user <strong id="sfs_01_0100__b141941718507">root</strong> to the non-<strong id="sfs_01_0100__b3636115195017">root</strong> user.</span><p><ol type="a" id="sfs_01_0100__ol17713949195013"><li id="sfs_01_0100__li18357757134711">Run the <strong id="sfs_01_0100__b1531193551612">chmod 777 /etc/sudoers</strong> command to change the <strong id="sfs_01_0100__b03437337178">sudoers</strong> file to be editable.</li><li id="sfs_01_0100__li1631735511536">Use the <strong id="sfs_01_0100__b057910175411">which</strong> command to view the <strong id="sfs_01_0100__b16352193017318">mount</strong> and <strong id="sfs_01_0100__b63511165517">umount</strong> command paths.<div class="fignone" id="sfs_01_0100__fig71849563558"><span class="figcap"><b>Figure 1 </b>Viewing command paths</span><br><span><img id="sfs_01_0100__image111845567557" src="en-us_image_0000001331394458.png" height="121.69500000000001" width="492.1" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="sfs_01_0100__li715217349512">Run the <strong id="sfs_01_0100__b18140232181594">vi /etc/resolv.conf</strong> command to edit the <strong id="sfs_01_0100__b84235270615915">sudoers</strong> file.</li><li id="sfs_01_0100__li17841124135610">Add a common user under the <strong id="sfs_01_0100__b1016110252502">root</strong> account. In this example, user <strong id="sfs_01_0100__b85521853131716">Mike</strong> is added.<div class="fignone" id="sfs_01_0100__fig1615624682112"><span class="figcap"><b>Figure 2 </b>Adding a user</span><br><span><img id="sfs_01_0100__image915610461212" src="en-us_image_0153998681.png" height="350.1225" width="492.1" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="sfs_01_0100__li715217349512">Run the <strong id="sfs_01_0100__b18140232181594">vi /etc/sudoers</strong> command to edit the <strong id="sfs_01_0100__b84235270615915">sudoers</strong> file.</li><li id="sfs_01_0100__li17841124135610">Add a common user under the <strong id="sfs_01_0100__b1016110252502">root</strong> account. In this example, user <strong id="sfs_01_0100__b85521853131716">Mike</strong> is added.<div class="fignone" id="sfs_01_0100__fig1615624682112"><span class="figcap"><b>Figure 2 </b>Adding a user</span><br><span><img id="sfs_01_0100__image915610461212" src="en-us_image_0153998681.png" height="350.1225" width="492.1" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="sfs_01_0100__li1491173310216">Press <strong id="sfs_01_0100__b51116037112652">Esc</strong>, input <strong id="sfs_01_0100__b58164000112657">:wq</strong>, and press <strong id="sfs_01_0100__b6357507311271">Enter</strong> to save and exit.</li><li id="sfs_01_0100__li379729692">Run the <strong id="sfs_01_0100__b1179445451819">chmod 440 /etc/sudoers</strong> command to change the <strong id="sfs_01_0100__b107981154101818">sudoers</strong> file to be read-only.</li></ol>
</p></li><li id="sfs_01_0100__li11734435318"><span>Log in to the ECS as user <strong id="sfs_01_0100__b13711123291915">Mike</strong>.</span></li><li id="sfs_01_0100__li340192251118"><span>Run the following command to mount the file system. For details about the mounting parameters, see <a href="#sfs_01_0100__table0741121164416">Table 1</a>.</span><p><p id="sfs_01_0100__p55415361311"><strong id="sfs_01_0100__b19826210105517">sudo mount -t nfs -o vers=3,timeo=600,noresvport,nolock</strong> <i><span class="varname" id="sfs_01_0100__varname8893193665014">Mount point</span></i> <i><span class="varname" id="sfs_01_0100__varname889483665017">Local path</span></i></p>
@ -26,7 +26,7 @@
</tr>
<tr id="sfs_01_0100__row125621115134717"><td class="cellrowborder" valign="top" width="17.080000000000002%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="sfs_01_0100__p1118632112125"><em id="sfs_01_0100__i47931287519">Local path</em></p>
</td>
<td class="cellrowborder" valign="top" width="82.92%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="sfs_01_0100__p10186182112124">Local path on the ECS, used to mount the file system, for example, <span class="filepath" id="sfs_01_0100__filepath56690752116"><b>/local_path</b></span>.</p>
<td class="cellrowborder" valign="top" width="82.92%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="sfs_01_0100__p10186182112124">A local directory on the ECS used to mount the file system, for example, <span class="filepath" id="sfs_01_0100__filepath13132410155018"><b>/local_path</b></span>.</p>
</td>
</tr>
</tbody>

8
docs/sfs/umn/sfs_01_0104.html
View File

@ -8,7 +8,13 @@
</th>
</tr>
</thead>
<tbody><tr id="sfs_01_0104__row1857891271114"><td class="cellrowborder" valign="top" width="17.669999999999998%" headers="mcps1.3.1.1.3.1.1 "><p id="sfs_01_0104__p15578131217114">2024-11-21</p>
<tbody><tr id="sfs_01_0104__row128921764610"><td class="cellrowborder" valign="top" width="17.669999999999998%" headers="mcps1.3.1.1.3.1.1 "><p id="sfs_01_0104__p204821512154618">2024-12-20</p>
</td>
<td class="cellrowborder" valign="top" width="82.33%" headers="mcps1.3.1.1.3.1.2 "><p id="sfs_01_0104__p19482131244620">Updated the following content:</p>
<p id="sfs_01_0104__p1675123335713">Added section <a href="sfs_01_0334.html">Managing SFS Turbo+OBS Storage Interworking</a>.</p>
</td>
</tr>
<tr id="sfs_01_0104__row1857891271114"><td class="cellrowborder" valign="top" width="17.669999999999998%" headers="mcps1.3.1.1.3.1.1 "><p id="sfs_01_0104__p15578131217114">2024-11-21</p>
</td>
<td class="cellrowborder" valign="top" width="82.33%" headers="mcps1.3.1.1.3.1.2 "><p id="sfs_01_0104__p857811217113">Updated the following content:</p>
<ul id="sfs_01_0104__ul99621931111110"><li id="sfs_01_0104__li7757451181115">Updated the maximum capacity of a <a href="sfs_01_0005.html#sfs_01_0005__table1763981963410">general purpose file system</a>.</li><li id="sfs_01_0104__li2962113131118">Added <a href="sfs_01_0069.html">What Are the Differences Between SFS, OBS, and EVS?</a></li><li id="sfs_01_0104__li7181104391117">Added <a href="sfs_01_0077.html">Can I Migrate My File System Data to Another Region?</a></li><li id="sfs_01_0104__li2076774319115">Added <a href="sfs_01_0078.html">Can a File System Be Mounted to Multiple Accounts?</a></li><li id="sfs_01_0104__li3340104491113">Added <a href="sfs_01_0111.html">Does SFS Support Cross-Region Mounting?</a></li><li id="sfs_01_0104__li9925194461113">Added <a href="sfs_01_0082.html">What Can I Do If Data of My File System Is Not the Same When Accessed from Two Client Servers?</a></li></ul>

2
docs/sfs/umn/sfs_01_0107.html
View File

@ -4,7 +4,7 @@
<div id="body1469764805160"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="en-us_topic_0037925065.html">Overview</a></strong><br>
<li class="ulchildlink"><strong><a href="sfs_01_0162.html">Overview</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="sfs_01_0134.html">Configure a VPC Endpoint</a></strong><br>
</li>

25
docs/sfs/umn/sfs_01_0162.html Normal file
View File

@ -0,0 +1,25 @@
<a name="sfs_01_0162"></a><a name="sfs_01_0162"></a>
<h1 class="topictitle1">Overview</h1>
<div id="body1474251606665"><p id="sfs_01_0162__p153145213519">This section describes how to use SFS.</p>
<p id="sfs_01_0162__p8060118">After creating a file system, you cannot directly access the file system. Instead, you need to mount the file system to ECSs.</p>
<p id="sfs_01_0162__p1096525020338"><a href="#sfs_01_0162__fig1830989795513">Figure 1</a> shows the process for creating and mounting an SFS Turbo file system.</p>
<p id="sfs_01_0162__p87441243173410"><a href="#sfs_01_0162__fig198881945142515">Figure 2</a> shows the process for creating and mounting an SFS Capacity-Oriented file system.</p>
<p id="sfs_01_0162__p1764452975911"><a href="#sfs_01_0162__fig22161519194012">Figure 3</a> shows the process for creating and mounting a general purpose file system.</p>
<div class="fignone" id="sfs_01_0162__fig1830989795513"><a name="sfs_01_0162__fig1830989795513"></a><a name="fig1830989795513"></a><span class="figcap"><b>Figure 1 </b>Process for using SFS Turbo</span><br><span><img id="sfs_01_0162__image41397385149" src="en-us_image_0153440615.png" height="443.943626" width="521.36" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="sfs_01_0162__fig198881945142515"><a name="sfs_01_0162__fig198881945142515"></a><a name="fig198881945142515"></a><span class="figcap"><b>Figure 2 </b>Process for using SFS Capacity-Oriented</span><br><span><img id="sfs_01_0162__image167373918312" src="en-us_image_0153455845.png" height="444.88500000000005" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
<div class="fignone" id="sfs_01_0162__fig22161519194012"><a name="sfs_01_0162__fig22161519194012"></a><a name="fig22161519194012"></a><span class="figcap"><b>Figure 3 </b>Process for using General Purpose File System</span><br><span><img id="sfs_01_0162__image32171192402" src="en-us_image_0000002053880478.png" height="513.7125" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0107.html">Getting Started</a></div>
</div>
</div>
<script language="JavaScript">
<!--
image_size('.imgResize');
var msg_imageMax = "view original image";
var msg_imageClose = "close";
//--></script>

2
docs/sfs/umn/en-us_topic_0033386660.html → docs/sfs/umn/sfs_01_0163.html
View File

@ -1,4 +1,4 @@
<a name="EN-US_TOPIC_0033386660"></a><a name="EN-US_TOPIC_0033386660"></a>
<a name="sfs_01_0163"></a><a name="sfs_01_0163"></a>
<h1 class="topictitle1">Introduction</h1>
<div id="body39451090"></div>

156
docs/sfs/umn/sfs_01_0334.html Normal file
View File

File diff suppressed because it is too large Load Diff

2
docs/sfs/umn/sfs_01_0346.html
View File

@ -11,7 +11,7 @@
</thead>
<tbody><tr id="sfs_01_0346__row43511042114557"><td class="cellrowborder" valign="top" width="24.060000000000002%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="sfs_01_0346__p34733515114557">Name</p>
</td>
<td class="cellrowborder" valign="top" width="75.94%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="sfs_01_0346__p61951365114557">Name of the file system, for example, <strong id="sfs_01_0346__b757017333594">sfs-name-001</strong></p>
<td class="cellrowborder" valign="top" width="75.94%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="sfs_01_0346__p61951365114557">Name of the created file system</p>
</td>
</tr>
<tr id="sfs_01_0346__row20417855154311"><td class="cellrowborder" valign="top" width="24.060000000000002%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="sfs_01_0346__p441795511431">Data Redundancy Policy</p>

6
docs/sfs/umn/sfs_01_0347.html
View File

@ -4,9 +4,9 @@
<div id="body0000001527141597"><p id="sfs_01_0347__p65596501154559">Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.</p>
<div class="section" id="sfs_01_0347__section39130845104113"><h4 class="sectiontitle">Prerequisites</h4><p id="sfs_01_0347__p22311411175">The file system to be deleted has been unmounted. For details about how to unmount the file system, see <a href="sfs_01_0026.html">Unmount a File System</a>.</p>
</div>
<div class="section" id="sfs_01_0347__section1880394195912"><h4 class="sectiontitle">Procedure</h4><ol id="sfs_01_0347__ol8890395161524"><li id="sfs_01_0347__li123464497"><span>Log in to the SFS console.</span></li><li id="sfs_01_0347__li526918348197"><span>In the file system list, locate the file system you want to delete and click <strong id="sfs_01_0347__b2623195816451">Delete</strong> in the <strong id="sfs_01_0347__b145361850124611">Operation</strong> column.</span><p><p id="sfs_01_0347__p0981123431913">If you want to delete more than one file system at a time, select the file systems, and then click <strong id="sfs_01_0347__b104861543466">Delete</strong> in the upper left part above the file system list. In the displayed dialog box, confirm the information and then click <strong id="sfs_01_0347__b848745414469">OK</strong>. Batch deletion is only supported for SFS Capacity-Oriented file systems. </p>
</p></li><li id="sfs_01_0347__li2423100101113"><span>In the displayed dialog box for an SFS Turbo file system, as shown in <a href="#sfs_01_0347__fig10624128141112">Figure 1</a>, confirm the information, enter <strong id="sfs_01_0347__b149981418513">DELETE</strong> in the text box, and click <strong id="sfs_01_0347__b1163721141912">OK</strong>.</span><p><p id="sfs_01_0347__p063784314139">In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click <strong id="sfs_01_0347__b654664911355">OK</strong>.</p>
<div class="p" id="sfs_01_0347__p235373520117"><div class="note" id="sfs_01_0347__note24565399154829"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="sfs_01_0347__p25886020154838">Only <strong id="sfs_01_0347__b981915347489">Available</strong> and <strong id="sfs_01_0347__b181953474815">Unavailable</strong> file systems can be deleted.</p>
<div class="section" id="sfs_01_0347__section1880394195912"><h4 class="sectiontitle">Procedure</h4><ol id="sfs_01_0347__ol8890395161524"><li id="sfs_01_0347__li123464497"><span>Log in to the SFS console.</span></li><li id="sfs_01_0347__li526918348197"><span>In the file system list, locate the file system you want to delete and click <strong id="sfs_01_0347__b1539264313499">Delete</strong> in the <strong id="sfs_01_0347__b145361850124611">Operation</strong> column.</span><p><p id="sfs_01_0347__p0981123431913">If you want to delete more than one file system at a time, select the file systems, and then click <strong id="sfs_01_0347__b104861543466">Delete</strong> in the upper left part above the file system list. In the displayed dialog box, confirm the information and then click <strong id="sfs_01_0347__b848745414469">OK</strong>. Batch deletion is only supported for SFS Capacity-Oriented file systems. </p>
</p></li><li id="sfs_01_0347__li2423100101113"><span>In the displayed dialog box for an SFS Turbo file system, as shown in <a href="#sfs_01_0347__fig10624128141112">Figure 1</a>, confirm the information, enter <strong id="sfs_01_0347__b335425824911">DELETE</strong> in the text box, and click <strong id="sfs_01_0347__b3354185811496">OK</strong>.</span><p><p id="sfs_01_0347__p063784314139">In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click <strong id="sfs_01_0347__b654664911355">OK</strong>.</p>
<div class="p" id="sfs_01_0347__p235373520117"><div class="note" id="sfs_01_0347__note24565399154829"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="sfs_01_0347__p25886020154838">Only file systems whose statuses are <strong id="sfs_01_0347__b429393685616">Available</strong> or <strong id="sfs_01_0347__b104731038155619">Creation failed</strong> can be deleted.</p>
</div></div>
<div class="fignone" id="sfs_01_0347__fig10624128141112"><a name="sfs_01_0347__fig10624128141112"></a><a name="fig10624128141112"></a><span class="figcap"><b>Figure 1 </b>Deleting an SFS Turbo file system</span><br><span><img id="sfs_01_0347__image96243289112" src="en-us_image_0000001921910840.png" height="309.225" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
</div>

44
docs/sfs/umn/sfs_01_0348.html Normal file
View File

@ -0,0 +1,44 @@
<a name="sfs_01_0348"></a><a name="sfs_01_0348"></a>
<h1 class="topictitle1">Mounting a File System Times Out</h1>
<div id="body1474254982340"><div class="section" id="sfs_01_0348__section41158684111639"><h4 class="sectiontitle">Symptom</h4><p id="sfs_01_0348__p39221336111646">When a file system is mounted to servers using the <strong id="sfs_01_0348__b3930153263314">mount</strong> command, message <span class="wintitle" id="sfs_01_0348__wintitle189381432143316"><b>timed out</b></span> is displayed.</p>
</div>
<div class="section" id="sfs_01_0348__section31326994111720"><h4 class="sectiontitle">Possible Causes</h4><ul id="sfs_01_0348__ul32705160105159"><li id="sfs_01_0348__li32662001105159">Cause 1: The network status is not stable.</li><li id="sfs_01_0348__li16790640105159">Cause 2: The network connection is abnormal.</li><li id="sfs_01_0348__li114712524443">Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.</li><li id="sfs_01_0348__li969295001614">Cause 4: The server that mounts the file system runs Ubuntu18 or later.</li></ul>
</div>
<div class="section" id="sfs_01_0348__section34776262111735"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="sfs_01_0348__p55755296111746">After the network fault is excluded, run the <strong id="sfs_01_0348__b842352706183951">mount</strong> command again.</p>
</div>
<div class="section" id="sfs_01_0348__section31191225111737"><h4 class="sectiontitle">Solution</h4><ul id="sfs_01_0348__ul16468151016343"><li id="sfs_01_0348__li54701410103415">Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.<p id="sfs_01_0348__p19600116173519"><a name="sfs_01_0348__li54701410103415"></a><a name="li54701410103415"></a>Re-mount the file system after the network issue is addressed.</p>
<ul id="sfs_01_0348__ul4438729153610"><li id="sfs_01_0348__li1743882910361">If the patch is uninstalled successfully, no further action is required.</li><li id="sfs_01_0348__li124412292361">If the problem persists, see the solution for cause 3.</li></ul>
</li><li id="sfs_01_0348__li74021740203710">Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.<ol id="sfs_01_0348__ol651519415380"><li id="sfs_01_0348__li399991613910">Check the DNS configuration of the tenant and run the <strong id="sfs_01_0348__b92419829511747">cat /etc/resolv.conf</strong> command.<ul id="sfs_01_0348__ul32101773912"><li id="sfs_01_0348__li1531117143917">If the DNS has not been configured, configure it. For details about how to configure the DNS, see <a href="sfs_01_0038.html">Configuring DNS</a>.</li><li id="sfs_01_0348__li44111720394">If the DNS has been configured, run the following command to check whether the DNS is correct:<p id="sfs_01_0348__p20781717396"><a name="sfs_01_0348__li44111720394"></a><a name="li44111720394"></a><strong id="sfs_01_0348__b0555941119">nslookup </strong><i><span class="varname" id="sfs_01_0348__varname13596931120">File system domain name</span></i></p>
<p id="sfs_01_0348__p147217123916">If the resolved IP address is in network segment <strong id="sfs_01_0348__b842352706111059">100</strong>, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to <a href="#sfs_01_0348__li19881703916">2</a>.</p>
</li></ul>
</li><li id="sfs_01_0348__li19881703916"><a name="sfs_01_0348__li19881703916"></a><a name="li19881703916"></a>Modify the <strong id="sfs_01_0348__b10377181015815">/etc/resolv.conf</strong> configuration file, configure the correct tenant DNS, and run <strong id="sfs_01_0348__b1377910982">vi /etc/resolv.conf</strong> to edit the <strong id="sfs_01_0348__b437717100813">/etc/resolv.conf</strong> file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.<div class="fignone" id="sfs_01_0348__fig42120175393"><span class="figcap"><b>Figure 1 </b>Configuring DNS</span><br><span><img id="sfs_01_0348__image0233178399" src="en-us_image_0147961692.png" width="NaN" height="NaN"></span></div>
<div class="p" id="sfs_01_0348__p22406822201147">The format is as follows:<pre class="screen" id="sfs_01_0348__screen1852931020934">nameserver 100.125.4.25</pre>
</div>
<ul id="sfs_01_0348__ul83161743911"><li id="sfs_01_0348__li43211179390">If the configuration succeeds, go to <a href="#sfs_01_0348__li1340101763913">3</a>.</li><li id="sfs_01_0348__li14331017163914">If the configuration fails, run the <strong id="sfs_01_0348__b842352706114229">lsattr /etc/resolv.conf</strong> command. If the information shown in <a href="#sfs_01_0348__fig93781793919">Figure 2</a> is displayed, the file is locked.<div class="fignone" id="sfs_01_0348__fig93781793919"><a name="sfs_01_0348__fig93781793919"></a><a name="fig93781793919"></a><span class="figcap"><b>Figure 2 </b>A locked file</span><br><span><img id="sfs_01_0348__image63814171394" src="en-us_image_0147961696.png" width="NaN" height="NaN"></span></div>
<p id="sfs_01_0348__p16391517183917">Run the <strong id="sfs_01_0348__b18872536487">chattr -i/etc/resolv.conf</strong> command to unlock the file. Then, re-configure the DNS and go to <a href="#sfs_01_0348__li1340101763913">3</a>.</p>
</li></ul>
</li><li id="sfs_01_0348__li1340101763913"><a name="sfs_01_0348__li1340101763913"></a><a name="li1340101763913"></a>Press <strong id="sfs_01_0348__b51116037112652">Esc</strong>, input <strong id="sfs_01_0348__b58164000112657">:wq</strong>, and press <strong id="sfs_01_0348__b6357507311271">Enter</strong> to save the changes and exit the vi editor.</li><li id="sfs_01_0348__li842131720393">The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See <a href="#sfs_01_0348__fig155441710394">Figure 3</a> and <a href="#sfs_01_0348__fig056217113912">Figure 4</a>.<div class="fignone" id="sfs_01_0348__fig155441710394"><a name="sfs_01_0348__fig155441710394"></a><a name="fig155441710394"></a><span class="figcap"><b>Figure 3 </b>VPC details</span><br><span><img id="sfs_01_0348__image0604174845710" src="en-us_image_0147961699.png" height="154.28" width="465.5" title="Click to enlarge" class="imgResize"></span></div>
<p id="sfs_01_0348__p1049405121818"></p>
<div class="fignone" id="sfs_01_0348__fig056217113912"><a name="sfs_01_0348__fig056217113912"></a><a name="fig056217113912"></a><span class="figcap"><b>Figure 4 </b>Modifying the DNS</span><br><span><img id="sfs_01_0348__image138726493221" src="en-us_image_0147961721.png" height="369.74" width="465.5" title="Click to enlarge" class="imgResize"></span></div>
</li><li id="sfs_01_0348__li565161723918">(Optional) Restart the server.</li><li id="sfs_01_0348__li7698171174518">Run the <strong id="sfs_01_0348__b27341193711">mount</strong> command again.<ul id="sfs_01_0348__ul1965433458"><li id="sfs_01_0348__li59744384511">If the problem is solved, no further action is required.</li><li id="sfs_01_0348__li310019432454">If the problem persists, see the solution for cause 4.</li></ul>
</li></ol>
</li><li id="sfs_01_0348__li333611319466">Cause 4: The server that mounts the file system runs Ubuntu18 or later.<ol id="sfs_01_0348__ol14992114884616"><li id="sfs_01_0348__li29921148104616">Reconfigure DNS by referring to <a href="sfs_01_0038.html">Configuring DNS</a>.</li><li id="sfs_01_0348__li37811357410">Check whether the target server running Ubuntu18 or later uses a private image.<ul id="sfs_01_0348__ul1258391396"><li id="sfs_01_0348__li5584211498">If yes, go to <a href="#sfs_01_0348__li199471275217">4</a>.</li><li id="sfs_01_0348__li5586711499">If no, go to <a href="#sfs_01_0348__li107041047680">3</a>.</li></ul>
</li><li id="sfs_01_0348__li107041047680"><a name="sfs_01_0348__li107041047680"></a><a name="li107041047680"></a>Convert the public image server to a private image server.<ol type="a" id="sfs_01_0348__ol11704114715811"><li id="sfs_01_0348__li57046472083"><a name="sfs_01_0348__li57046472083"></a><a name="li57046472083"></a>To create a private image based on an existing ECS, see section "Creating an Image" in the <em id="sfs_01_0348__i1816631044">Elastic Cloud Server User Guide</em>.</li><li id="sfs_01_0348__li487420128456">Use the private image created in <a href="#sfs_01_0348__li57046472083">3.a</a> to create an ECS or change the ECS OS. For details, see section "Changing the OS" in the <em id="sfs_01_0348__i6673536286">Elastic Cloud Server User Guide</em>.</li></ol>
</li><li id="sfs_01_0348__li199471275217"><a name="sfs_01_0348__li199471275217"></a><a name="li199471275217"></a>Log in to the server and mount the file system again.</li></ol>
</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>