forked from docs/doc-exports
Zaoxu, Li
305c41bb57
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Zaoxu, Li <lizaoxu@huawei.com> Co-committed-by: Zaoxu, Li <lizaoxu@huawei.com>
175 lines
23 KiB
HTML
175 lines
23 KiB
HTML
<a name="evs_01_0034"></a><a name="evs_01_0034"></a>
|
|
|
|
<h1 class="topictitle1">Initializing a Linux Data Disk (parted)</h1>
|
|
<div id="body1511319979089"><div class="section" id="evs_01_0034__section31580524185332"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0034__p4699546795037">This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to <span id="evs_01_0034__text1146380502125328">a server</span> running Linux and use parted to partition the data disk.</p>
|
|
<p id="evs_01_0034__p433451952110">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
|
<p id="evs_01_0034__p4630584010514">The method for initializing a disk varies depending on the OS running on the <span id="evs_01_0034__evs_01_0033_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
|
|
</div>
|
|
<div class="section" id="evs_01_0034__section36737034185332"><h4 class="sectiontitle">Prerequisites</h4><ul id="evs_01_0034__evs_01_0108_ul28913191171813"><li id="evs_01_0034__evs_01_0108_li20771164724419">A data disk has been attached to <span id="evs_01_0034__evs_01_0108_text184241938124418">a server</span> and has not been initialized.</li><li id="evs_01_0034__evs_01_0108_li36962755115557">You have logged in to the <span id="evs_01_0034__evs_01_0108_text25940422717248">server</span>.<ul id="evs_01_0034__evs_01_0108_ul6229092211568"><li id="evs_01_0034__evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="evs_01_0034__evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="evs_01_0034__evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="evs_01_0034__evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="evs_01_0034__section36039836195351"><h4 class="sectiontitle">Creating and Mounting a Partition</h4><p id="evs_01_0034__p4530289419544">The following example shows you how a new partition can be created on a new data disk that has been attached to <span id="evs_01_0034__text2422957163556">a server</span>. The partition will be created using parted, and GPT is used as the partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on <strong id="evs_01_0034__b109171540101711">/mnt/sdc</strong>, and configured automatic mounting at system start.</p>
|
|
</div>
|
|
<ol id="evs_01_0034__ol1329192162914"><li id="evs_01_0034__li02952152918"><span>Run the following command to query information about the new data disk:</span><p><p id="evs_01_0034__p6233165017299"><strong id="evs_01_0034__b401898111841">lsblk</strong></p>
|
|
<div class="p" id="evs_01_0034__p1861313818316">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen841414913434">root@ecs-test-0001 ~]# lsblk
|
|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
|
vda 253:0 0 40G 0 disk
|
|
└─vda1 253:1 0 40G 0 part /
|
|
vdb 253:16 0 100G 0 disk</pre>
|
|
</div>
|
|
<p id="evs_01_0034__p944866918517">In the command output, <span id="evs_01_0034__text151478292215509">the server</span> contains two disks. <span class="parmname" id="evs_01_0034__parmname183835084719318"><b>/dev/vda</b></span> is the system disk, and <span class="parmname" id="evs_01_0034__parmname46787022319330"><b>/dev/vdb</b></span> is the new data disk.</p>
|
|
</p></li><li id="evs_01_0034__li17578198183210"><span>Run the following command to enter parted to partition the new data disk:</span><p><p id="evs_01_0034__p19915181441219"><strong id="evs_01_0034__b162582328145953">parted</strong> <em id="evs_01_0034__i1217464476145953">New data disk</em></p>
|
|
<p id="evs_01_0034__p41477006111223">In this example, run the following command:</p>
|
|
<p id="evs_01_0034__p175788883211"><strong id="evs_01_0034__b879811371446">parted /dev/vdb</strong></p>
|
|
<div class="p" id="evs_01_0034__p2057812811323">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen538012914513">[root@ecs-test-0001 ~]# parted /dev/vdb
|
|
GNU Parted 3.1
|
|
Using /dev/vdb
|
|
Welcome to GNU Parted! Type 'help' to view a list of commands.
|
|
(parted) </pre>
|
|
</div>
|
|
</p></li><li id="evs_01_0034__li125780811321"><span>Enter <strong id="evs_01_0034__b43545514131720">p</strong> and press <strong id="evs_01_0034__b56365313131720">Enter</strong> to view the current disk partition style.</span><p><div class="p" id="evs_01_0034__p29271455221812">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen137411040463">(parted) p
|
|
Error: /dev/vdb: unrecognised disk label
|
|
Model: Virtio Block Device (virtblk)
|
|
Disk /dev/vdb: 107GB
|
|
Sector size (logical/physical): 512B/512B
|
|
Partition Table: unknown
|
|
Disk Flags:
|
|
(parted) </pre>
|
|
</div>
|
|
<p id="evs_01_0034__p4012741718421">In the command output, the <strong id="evs_01_0034__b1148445363815">Partition Table</strong> value is <strong id="evs_01_0034__b592417555382">unknown</strong>, indicating that no partition style is set for the new disk.</p>
|
|
</p></li><li id="evs_01_0034__li51339901112856"><span>Run the following command to set the disk partition style:</span><p><p id="evs_01_0034__p9393560112945"><strong id="evs_01_0034__b1848002532151728">mklabel</strong> <em id="evs_01_0034__i1998704360151728">Disk partition style</em></p>
|
|
<p id="evs_01_0034__p5919528411302">In this example, run the following command to set the partition style to GPT: (Disk partition styles can be MBR or GPT.)</p>
|
|
<p id="evs_01_0034__p11418922112925"><strong id="evs_01_0034__b17959944112933">mklabel gpt</strong></p>
|
|
<div class="notice" id="evs_01_0034__note18848725104723"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0034__evs_01_0038_p11834286151113">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.</p>
|
|
<p id="evs_01_0034__evs_01_0038_p612681541585">If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.</p>
|
|
</div></div>
|
|
</p></li><li id="evs_01_0034__li17114528113148"><span>Enter <strong id="evs_01_0034__b1695801853151835">p</strong> and press <strong id="evs_01_0034__b188005457151835">Enter</strong> to view the disk partition style.</span><p><div class="p" id="evs_01_0034__p19813031113148">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen1333873825111">(parted) mklabel gpt
|
|
(parted) p
|
|
Model: Virtio Block Device (virtblk)
|
|
Disk /dev/vdb: 107GB
|
|
Sector size (logical/physical): 512B/512B
|
|
Partition Table: gpt
|
|
Disk Flags:
|
|
|
|
Number Start End Size File system Name Flags
|
|
|
|
(parted) </pre>
|
|
</div>
|
|
<p id="evs_01_0034__p16339115010516">In the command output, the <strong id="evs_01_0034__b842352706151643">Partition Table</strong> value is <strong id="evs_01_0034__b842352706151622">gpt</strong>, indicating that the disk partition style is GPT.</p>
|
|
</p></li><li id="evs_01_0034__li2274037316228"><span>Enter <strong id="evs_01_0034__b842352706204829">unit s</strong> and press <strong id="evs_01_0034__b842352706204833">Enter</strong> to set the measurement unit of the disk to sector.</span></li><li id="evs_01_0034__li17033373105032"><span>Run the following command and press <strong id="evs_01_0034__b842352706151952">Enter</strong>:</span><p><p id="evs_01_0034__p1798722809"><strong id="evs_01_0034__b167419798">mkpart</strong> <em id="evs_01_0034__i39514141897">Partition name Start sector</em> <em id="evs_01_0034__i795119141913">End sector</em></p>
|
|
<p id="evs_01_0034__p96086206616">In this example, run the following command:</p>
|
|
<p id="evs_01_0034__p630617311785"><strong id="evs_01_0034__b99791930996">mkpart test 2048s 100%</strong></p>
|
|
<p id="evs_01_0034__p6516336113613">In this example, one partition is created for the new data disk. Variable <em id="evs_01_0034__i842352697185932">2048s</em> indicates the disk start sector, and variable <em id="evs_01_0034__i842352697185948">100%</em> indicates the disk end sector. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.</p>
|
|
<div class="p" id="evs_01_0034__p3579681322">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen8579158143210">(parted) mkpart opt 2048s 100%
|
|
(parted)</pre>
|
|
</div>
|
|
</p></li><li id="evs_01_0034__li457988173211"><span>Enter <strong id="evs_01_0034__b171797972153053">p</strong> and press <strong id="evs_01_0034__b907230253153053">Enter</strong> to view details about the new partition.</span><p><div class="p" id="evs_01_0034__p157919863211">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen044361613111">(parted) p
|
|
Model: Virtio Block Device (virtblk)
|
|
Disk /dev/vdb: 209715200s
|
|
Sector size (logical/physical): 512B/512B
|
|
Partition Table: gpt
|
|
Disk Flags:
|
|
|
|
Number Start End Size File system Name Flags
|
|
1 2048s 209713151s 209711104s test
|
|
|
|
(parted) </pre>
|
|
</div>
|
|
</p></li><li id="evs_01_0034__li4398403895019"><span>Enter <strong id="evs_01_0034__b198198625115314">q</strong> and press <strong id="evs_01_0034__b212127154015314">Enter</strong> to exit parted.</span><p><div class="p" id="evs_01_0034__p388845720177">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen18254819161811">(parted) q
|
|
Information: You may need to update /etc/fstab.</pre>
|
|
</div>
|
|
<p id="evs_01_0034__p145861541111818">You can set automatic disk mounting by updating the <strong id="evs_01_0034__b1858793314478">/etc/fstab</strong> file. Before updating the file, set the file system format for the partition and mount the partition on the mount point.</p>
|
|
</p></li><li id="evs_01_0034__li21640013114439"><span>Run the following command to view the disk partition information:</span><p><p id="evs_01_0034__p60542391114439"><strong id="evs_01_0034__b8010609114439">lsblk</strong></p>
|
|
<div class="p" id="evs_01_0034__p4986620114439">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen10760108181215">[root@ecs-test-0001 ~]# lsblk
|
|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
|
vda 253:0 0 40G 0 disk
|
|
└─vda1 253:1 0 40G 0 part /
|
|
vdb 253:16 0 100G 0 disk
|
|
└─vdb1 253:17 0 100G 0 part</pre>
|
|
</div>
|
|
<p id="evs_01_0034__p48773852105546">In the command output, <strong id="evs_01_0034__b842352706161344">/dev/vdb1</strong> is the partition you created.</p>
|
|
</p></li><li id="evs_01_0034__li958068193210"><span>Run the following command to set the file system format for the new partition:</span><p><p id="evs_01_0034__p1169510295739"><strong id="evs_01_0034__b59009069215057">mkfs</strong> <strong id="evs_01_0034__b189101114715057">-t</strong> <em id="evs_01_0034__i22062884215057">File system format</em> <strong id="evs_01_0034__b123674698515057">/dev/vdb1</strong></p>
|
|
<p id="evs_01_0034__p5243126995731">In this example, run the following command to set the <span class="filepath" id="evs_01_0034__filepath14618406891372"><b>ext4</b></span> file system for the new partition:</p>
|
|
<p id="evs_01_0034__p1580148193210"><strong id="evs_01_0034__b2150362315270">mkfs -t ext4 /dev/vdb1</strong></p>
|
|
<div class="p" id="evs_01_0034__p458016833215">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen01161834181220">[root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
|
|
mke2fs 1.42.9 (28-Dec-2013)
|
|
Filesystem label=
|
|
OS type: Linux
|
|
Block size=4096 (log=2)
|
|
Fragment size=4096 (log=2)
|
|
Stride=0 blocks, Stripe width=0 blocks
|
|
6553600 inodes, 26213888 blocks
|
|
1310694 blocks (5.00%) reserved for the super user
|
|
First data block=0
|
|
Maximum filesystem blocks=2174746624
|
|
800 block groups
|
|
32768 blocks per group, 32768 fragments per group
|
|
8192 inodes per group
|
|
Superblock backups stored on blocks:
|
|
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
|
|
4096000, 7962624, 11239424, 20480000, 23887872
|
|
|
|
Allocating group tables: done
|
|
Writing inode tables: done
|
|
Creating journal (32768 blocks): done
|
|
Writing superblocks and filesystem accounting information: done</pre>
|
|
</div>
|
|
<p id="evs_01_0034__p1758015813211">The formatting takes a period of time. Observe the system running status and do not exit.</p>
|
|
<div class="notice" id="evs_01_0034__note29186911243"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0034__p262682811243">The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.</p>
|
|
</div></div>
|
|
</p></li><li id="evs_01_0034__li1910362714149"><span>Run the following command to create a mount point:</span><p><p id="evs_01_0034__p1910382791412"><strong id="evs_01_0034__b1856120194514">mkdir</strong> <em id="evs_01_0034__i956219198512">Mount point</em></p>
|
|
<p id="evs_01_0034__p810320277141">In this example, run the following command to create the <strong id="evs_01_0034__b2288210513">/mnt/sdc</strong> mount point:</p>
|
|
<p id="evs_01_0034__p171039270143"><strong id="evs_01_0034__b1110352719144">mkdir /mnt/sdc</strong></p>
|
|
</p></li><li id="evs_01_0034__li17103172711414"><span>Run the following command to mount the new partition on the created mount point:</span><p><p id="evs_01_0034__p31039277141"><strong id="evs_01_0034__b16411837205110">mount</strong> <em id="evs_01_0034__i8642173720513">Disk partition</em> <em id="evs_01_0034__i56430370511">Mount point</em></p>
|
|
<p id="evs_01_0034__p171037271142">In this example, run the following command to mount the new partition <strong id="evs_01_0034__b970419398517">/dev/vdb1</strong> on <strong id="evs_01_0034__b11705143913515">/mnt/sdc</strong>:</p>
|
|
<p id="evs_01_0034__p51031027171414"><strong id="evs_01_0034__b5103122710147">mount /dev/vdb1 /mnt/sdc</strong></p>
|
|
</p></li><li id="evs_01_0034__li47695742151459"><span>Run the following command to view the mount result:</span><p><p id="evs_01_0034__p26608495151459"><strong id="evs_01_0034__b38149863151459">df -TH</strong></p>
|
|
<p id="evs_01_0034__p7804447151459">Information similar to the following is displayed:</p>
|
|
<pre class="screen" id="evs_01_0034__screen18302978112619">[root@ecs-test-0001 ~]# df -TH
|
|
Filesystem Type Size Used Avail Use% Mounted on
|
|
/dev/vda1 ext4 43G 1.9G 39G 5% /
|
|
devtmpfs devtmpfs 2.0G 0 2.0G 0% /dev
|
|
tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm
|
|
tmpfs tmpfs 2.0G 9.0M 2.0G 1% /run
|
|
tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
|
|
tmpfs tmpfs 398M 0 398M 0% /run/user/0
|
|
/dev/vdb1 ext4 106G 63M 101G 1% /mnt/sdc</pre>
|
|
<p id="evs_01_0034__p8231156151459">New partition <span class="parmname" id="evs_01_0034__parmname1012184233182948"><b>/dev/vdb1</b></span> is mounted on <span class="filepath" id="evs_01_0034__filepath1018173411182954"><b>/mnt/sdc</b></span>.</p>
|
|
<div class="note" id="evs_01_0034__note151217575408"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0034__p13141357194019">If the <span id="evs_01_0034__text912616305210">server</span> is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the <strong id="evs_01_0034__b18510177115212">/etc/fstab</strong> file. For details, see <a href="#evs_01_0034__section15839912195453">Setting Automatic Mounting at System Start</a>.</p>
|
|
</div></div>
|
|
</p></li></ol>
|
|
<div class="section" id="evs_01_0034__section15839912195453"><a name="evs_01_0034__section15839912195453"></a><a name="section15839912195453"></a><h4 class="sectiontitle">Setting Automatic Mounting at System Start</h4><p id="evs_01_0034__evs_01_0033_p10888449418">Modify the <strong id="evs_01_0034__evs_01_0033_b638544071512">fstab</strong> file to set automatic disk mounting at server start. You can also set automatic mounting for the <span id="evs_01_0034__evs_01_0033_text615861019358">server</span>s containing data. This operation will not affect the existing data.</p>
|
|
<p id="evs_01_0034__evs_01_0033_p3301097119558">The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the <strong id="evs_01_0034__evs_01_0033_b1250394412233">fstab</strong> file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during <span id="evs_01_0034__evs_01_0033_text60279752174534">the server</span> stop or start, resulting in improper <span id="evs_01_0034__evs_01_0033_text33232815911">server</span> running after restart.</p>
|
|
<div class="note" id="evs_01_0034__evs_01_0033_note6058396910219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0034__evs_01_0033_p838481110219">UUID is the unique character string for disk partitions in a Linux system.</p>
|
|
</div></div>
|
|
<ol id="evs_01_0034__evs_01_0033_ol7409641133211"><li id="evs_01_0034__evs_01_0033_li840964143216"><span>Run the following command to query the partition UUID:</span><p><p id="evs_01_0034__evs_01_0033_p32760575102436"><strong id="evs_01_0034__evs_01_0033_b810771306145914">blkid</strong> <em id="evs_01_0034__evs_01_0033_i1994655083145914">Disk partition</em></p>
|
|
<p id="evs_01_0034__evs_01_0033_p54606997105845">In this example, run the following command to query the UUID of the <span class="parmname" id="evs_01_0034__evs_01_0033_parmname2013759973122928"><b>/dev/vdb1</b></span> partition:</p>
|
|
<p id="evs_01_0034__evs_01_0033_p204811453103215"><strong id="evs_01_0034__evs_01_0033_b11565159153817">blkid /dev/vdb1</strong></p>
|
|
<p id="evs_01_0034__evs_01_0033_p13610514113319">Information similar to the following is displayed:</p>
|
|
<pre class="screen" id="evs_01_0034__evs_01_0033_screen361091453315">[root@ecs-test-0001 ~]# blkid /dev/vdb1
|
|
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"</pre>
|
|
<p id="evs_01_0034__evs_01_0033_p275684701890">The UUID of the <span class="parmname" id="evs_01_0034__evs_01_0033_parmname860990818858"><b>/dev/vdb1</b></span> partition is displayed.</p>
|
|
</p></li><li id="evs_01_0034__evs_01_0033_li199421823183318"><span>Run the following command to open the <strong>fstab</strong> file using the vi editor:</span><p><p id="evs_01_0034__evs_01_0033_p9610114153320"><strong id="evs_01_0034__evs_01_0033_b1361031419337">vi /etc/fstab</strong></p>
|
|
</p></li><li id="evs_01_0034__evs_01_0033_li941511389331"><span>Press <strong>i</strong> to enter the editing mode.</span></li><li id="evs_01_0034__evs_01_0033_li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0034__evs_01_0033_b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0034__evs_01_0033_screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
|
</p></li><li id="evs_01_0034__evs_01_0033_li841512388338"><span>Press <strong id="evs_01_0034__evs_01_0033_b8348192418548">Esc</strong>, enter <strong id="evs_01_0034__evs_01_0033_b15351152418546">:wq</strong>, and press <strong id="evs_01_0034__evs_01_0033_b7353142416544">Enter</strong>.</span><p><p id="evs_01_0034__evs_01_0033_p1141543813310">The system saves the configurations and exits the vi editor.</p>
|
|
</p></li><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li17720613102410"><span>Perform the following operations to verify the automatic mounting function:</span><p><ol type="a" id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_ol199891910256"><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li1620791415268">Run the following command to unmount the partition:<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p18208131462618"><a name="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><a name="evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><strong id="evs_01_0034__evs_01_0033_b1708526520162011">umount</strong> <em id="evs_01_0034__evs_01_0033_i1458842329162011">Disk partition</em></p>
|
|
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p621161413262">In this example, run the following command:</p>
|
|
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p1521115148260"><strong id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_b0213614192618">umount /dev/vdb1</strong></p>
|
|
</li><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li2397162792610">Run the following command to reload all the content in the <strong id="evs_01_0034__evs_01_0033_b842352706104731">/etc/fstab</strong> file:<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p1739714278269"><strong id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_b63981278267">mount -a</strong></p>
|
|
</li><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li9280203710269">Run the following command to query the file system mounting information:<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p3282133715264"><a name="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><a name="evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><strong id="evs_01_0034__evs_01_0033_b1187012852919">mount</strong> <strong id="evs_01_0034__evs_01_0033_b17601123382916">|</strong> <strong id="evs_01_0034__evs_01_0033_b1070716324521">grep</strong> <em id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_i2284337112614">Mount point</em></p>
|
|
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p3286437112619">In this example, run the following command:</p>
|
|
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p18286123782619"><strong id="evs_01_0034__evs_01_0033_b925094342911">mount</strong> <strong id="evs_01_0034__evs_01_0033_b1725119437291">|</strong> <strong id="evs_01_0034__evs_01_0033_b15324154395212">grep</strong> <strong id="evs_01_0034__evs_01_0033_b1831387417">/mnt/sdc</strong></p>
|
|
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, the automatic mounting function takes effect:</p>
|
|
<pre class="screen" id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_screen429312370265">root@ecs-test-0001 ~]# mount | grep /mnt/sdc
|
|
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)</pre>
|
|
</li></ol>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0058.html">Initialize an EVS Data Disk</a></div>
|
|
</div>
|
|
</div>
|
|
|