Comparison of disk management between Windows and Linux systems

The booming of the information age has brought about an explosive growth in the amount of data. Of course, a very hot topic is how to store data. From the time we buy back a disk, to the point where it can actually store the data, what do we need for our administrators? This is closely related to the type of operating system
, different operating system
management method is different, for windows system, first need to install the disk to the computer hardware, then Open the windows system, open the disk management to find the newly added disk, online - initialize - new volume - assign drive letter - format, and then directly open the file explorer, you can store data in the corresponding partition, it is not difficult . For the Linux system, it is not complicated. Although the Linux system has a rich graphical interface like the Windows system, in fact, we usually complete various management tasks under the command line, and the disk under the Linux system. Management is not complicated, just the characteristics of all files under Linux determine that it is slightly more complicated to use than Windows. It needs to be partitioned first, then formatted, and finally it needs to be mounted to the corresponding directory. There is one more step than Windows, so which commands do you need to implement? In this section, we will experiment to demonstrate the unique charm of two different operating systems, from the beginning of the installation, to the end of the data storage. Windows
System Disk Basic Management: Experimental Environment: VMware's virtualization platform, a virtual machine SVR1 with Windows Server 2012R2 operating system installed. Step 1: Add a disk to SVR1 using VMware's platform. Open the VMware platform, select the SVR1 right button, select Settings, click Add, open the virtual disk add wizard, and follow the wizard's default settings to add a 60GB virtual disk step by step. The second step: boot the disk partition format until the final use 1, open SVR1, log in with the administrator account, open the run with windows + R shortcuts, enter diskmgmt.msc to open the disk management, you can see an extra piece Mark the disk with the red down arrow, then select the right mouse button - online, then right click - initialize the disk, the MBR partition format is selected by default, and the red mark disappears when done.
2, select the blank right of 60GB unallocated space, create a new simple volume, pop up the new simple volume wizard, follow the wizard, specify the volume size 20480M, drive letter E, format the file system type is NTFS, then carry out. You will see an extra 20GB disk partition, and then open the file explorer to see an E disk partition, you can store file data in it. Disk management under Linux system: (The results in the experiment may show too long, only the key parts are displayed.) Experimental environment: VMware's virtualization platform, a virtual machine Linux 7.0-1 with Rethat Enterprise Linux 7.0 installed. The first step: based on the VMware platform, add a SCSI type virtual disk for Linux7.0-1. Add a disk to the Linux system virtual machine. The same as Windows, refer to the procedure for adding virtual disk to SVR1, which is not demonstrated here. Add a 20GB virtual disk to Linux7.0-1. Step 2: Open Linux7.0-1, log in as the root user, and use the fdisk -l command to check the status of the virtual machine disk partition. You can see that there is more than one disk on the current virtual machine and no partitions are made. Step 3: Create a primary partition and a logical partition for the /dev/sdb disk using the fdisk command. At the shell prompt, after entering fdisk /dev/sdb, enter n to create a new partition, p to specify the partition type as the primary partition, 1 to specify the partition number, and carriage return to select the default starting sector, +200M specified The size of the partition, after completion, will create a 200M size of the primary partition, the same method, continue to enter n – e – Enter & ndash; Enter & ndash; Enter, the remaining space is created as an extended partition, with p to view the created partition, and then remember to use the w option to save and exit. (In fact, there are some commonly used options, such as using t to specify the type of file system, using d to delete the partition, using q in case of misoperation without saving, etc.) Step 4: Using partprobe /dev/The sdb command starts the kernel to re-read the new partition table. Step 5: Format the new partition /dev/sdb1 with mkfs.ext4 /dev/sdb1 or mkfs –t ext4 /dev/sdb1 command to partition sdb1 The file system type formatted as ext4. Step 6: Mount the new partition /dev/sdb1 1. Create the directory to be mounted with the mkdir /test command. 2. Mount the newly created partition to the corresponding directory with the mount /dev/sdb1 /test command. Temporary mount, the mount fails after the system restarts. 3. Use vi /etc/fstab to edit the file and add the mount record to achieve boot automatic mount. Here is a brief explanation of the meaning of adding records in the file: the first column /dev/sdb1 stands for The file system or storage device to be mounted; the second column /test represents the directory to be mounted; the third column ext4 represents the file system type of the partition; the fourth column defaults represents the default mount options, such as only superusers, Automatically mount with read and write permissions; the last two 0, the fifth column of 0 means ignore the dump backup operation (1 represents backup); the sixth column of 0 represents the order of the power-on self-test, 0 means not self-test, 1 represents Check the root partition. Other partitions use 2, 3… …. The smaller the number, the higher the self-test. 4. Use the df -h command to view the result of the mount. 5. Use the cd /test command to switch to the mounted /test directory to create a file. You can see that you can create file 1 in the /test directory. And see the lost+found in the directory, indicating that it is indeed the directory after the successful mount. Based on the above content, we found that the operation methods of implementing disk management in Windows or Linux are similar, but in different ways. In fact, administrators who have done disk management know that disk management is far from simple. For example, in the process of disk management, it may be reasonable to set up disk partitions. The disk partition space is almost full, how can I adjust the size of the disk partition? The disk array that I used to do is not very easy to use. I want to adjust the RAID level. What should I do? … … such problems are endless, in the face of such troubles, how to solve as an administrator

In the previous section of the Windows and Linux system disk management comparison dialysis (a), we learned two different The basic application management of the operating system disk is different, but in the actual environment, the management of the disk is far from simple. The administrator who manages the disk storage may know how to plan the partition size in disk management. What should I do if the partitioned disk partition space is insufficient? I want to replace the structure of the disk array, how to operate? The troubles such as this are annoying. The solution to these problems is often through the use of symbolic links, or the use of tools to adjust the size of the partition, etc., but these are temporary solutions, and have not fundamentally solved the problem, with windows The emergence of storage space in server2012, the emergence of LVM under Linux, these problems have been solved. Then in this section we will focus on the windows server2012 environment, through the storage space configuration process to understand the storage space to achieve disk management flexibility, will also be based on the Linux 7.0 environment to achieve the management of logical volumes under Linux, and thus contrast There are two ways to achieve the difference and charm of disk management. For Windows systems, administrators often use disk arrays to increase the availability of disks on the server, choosing the appropriate RAID level for high availability. But we know that the disk array is working under the operating system, you need to plan RAID before installing the operating system, then the problem is, if the RAID has been planned and is already in use, but now I want to change the RAID level, I should How to do it? At this point, we need to reboot, then re-planning the RAID configuration, reinstalling the operating system, and it is very cumbersome to implement. So is there a simplified solution that can replace RAID well and implement it quickly? Before Windows Server 2012, there was no way to solve it. After Windows Server 2012, a new function called storage space appeared. It runs on the operating system and realizes the approximate RAID function through the storage space. Next, the deployment process of the storage space will be demonstrated experimentally. Management of storage space under Windows system: Experimental environment: VMware's virtualization platform, a virtual machine SVR1 with Windows server2012R2 operating system installed. The first step: adding virtual disk to virtual machine SVR1 to add virtual disk process can refer to windows and Linux system disk management comparison dialysis (a). After the addition is complete, select the file and storage service-storage pool on the left in Server Manager, and then you will see three areas in the open interface for the storage pool, virtual disk, physical disk and see in the physical disk box. There are three newly added disks with a size of 60GB, and three more disks can be seen in local disk management. Step 2: Create a new storage pool based on the current three physical disks. In the blank area of ​​the storage pool area, right-click, create a new storage pool, open the storage pool new wizard, and specify the name of the storage pool, such as pool; select the storage pool. Physical disks, such as three are selected, and the assigned type is selected automatically. Here, hot spare and manual refer to whether the disk will be automatically switched or manually switched when the other disk fails. The way to achieve replacement, here we choose the way of automatic allocation. Then the next step, the last one is created. After the storage pool is created successfully, select the created storage pool pool in the Server Manager-Storage Pool interface. You can see that three physical disks have been added to the storage pool and become pooled resources. You can try to open local disk management. I found that three disks could not be seen. Step 3: Create a virtual disk based on the storage pool 1. Locate the virtual disk area, select Task - New Virtual Disk or directly select the New Virtual Disk Wizard, open the wizard for creating a new virtual disk, and then specify the name of the virtual disk vd1, then let us Select the layout mode of the data stored in the virtual disk in the physical disk, simple represents RAID0, mirror represents RAID1, parity represents RAID5, we can choose simple here, set the type selection to be streamlined, the specified size is 10GB, and finally choose to create.
2, after clicking Close, the New Volume Wizard will pop up automatically. This step is mainly to partition and format the newly created virtual disk. Here, specify the server and disk on which the volume is created, specify the size of the new volume, the drive letter, etc. Here we keep the default. Click Close when done, and the newly created virtual disk vd1 will be displayed in the virtual disk area. The fourth step: the management of storage space