The 3 virtual machines are all 20G disks. It is not enough to use them, so I expanded one first, all kinds of Baidu... All kinds of pits, everyone's situation is different, and I found the different places and finally checked Baidu immediately. After a successful expansion, I plan to expand another one to keep a record. (I use the xshell superuser to link the virtual machine)
Expansion is roughly divided into 3 steps: 1. External settings; 2. Setting partitions ; 3. Rebooting ; 4 Mounting ; You can solve these problems at one time)
1. Shut down the virtual machine (not suspend ), click "Virtual Machine/Settings", select "Hard Disk", and expand the capacity to 40G
2. Start the virtual machine, enter the linux system as root user, and add a new partition
2.1 View the current partition status
[root@slave1 /root]$ fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000381a8
Device Boot Start End Blocks Id System
/dev/sda1 * 1 39 307200 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 39 2358 18631680 83 Linux
/dev/sda3 2358 2611 2031616 82 Linux swap / Solaris
The current largest partition is sda3 and the newly created partition is sda4 . (please note the emphasis)
2.2 Enter the following command
[root@slave1 /root]$ fdisk /dev/sda
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): m #2.3命令行提示下输入【m】
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): n #Enter the command [n] to add a new partition
Command action
e extended
p primary partition (1-4)
p #Enter the command [p] to create a primary partition .
Selected partition 4
First cylinder (2611-5221, default 2611): #Enter Using
default value 2611
Last cylinder, +cylinders or +size{K,M,G} (2611-5221, default 5221): #Enter Using
default value 5221
Command (m for help): w #输入【w】保存
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
[root@slave1 /]$ mkdir disk4 [root@slave1 /]$ mount /dev/sda4 /disk4 mount: you must specify the filesystem type
An error occurred when mounting, look at the red font, the reason may be that there is no physical volume, volume group , logical volume, formatting (4.1, 4.2, 4.3 are mainly used to solve these three problems)
4.1 View physical volumes:
[root@slave1 /]$ pvs
No output! ! ! Indicates that there is no physical volume, the created partition is sda4 , and a physical volume is created for this partition.
[root@slave1 /]$ pvcreate /dev/sda4 Physical volume "/dev/sda4" successfully created
Check the physical volume at this time, ok
[root@slave1 /]$ pvs PV VG Fmt Attr PSize PFree /dev/sda4 lvm2 a-- 19.99g 19.99g
4.2 View volume group
[root@slave1 /]$ vgs
No volume groups found
Error, no, first create volume group vgdata
[root@slave1 /]$ vgcreate vgdata /dev/sda4 Volume group "vgdata" successfully created
Check the volume group again, OK! ! !
[root@slave1 /]$ vgs VG #PV #LV #SN Attr VSize VFree vgdata 1 1 0 wz--n- 19.99g 15.09g [root@slave1 /]$ vgdisplay --- Volume group --- VG Name vgdata System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 2 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 19.99 GiB PE Size 4.00 MiB Total PE 5118 Alloc PE / Size 1255 / 4.90 GiB Free PE / Size 3863 / 15.09 GiB VG UUID f8keeP-x5yH-qdfd-9roM-hbAt-ALEI-yYG4wB
4.3 View logical volumes
[root@slave1 /]$ lvdisplay No volume groups found
Error, no, create logical volume
[root@slave1 /]$ lvcreate -L4.9G vgdata -n lvolhome /dev/sda4 Rounding up size to full physical extent 4.90 GiB Logical volume "lvolhome" created
Check the creation result, OK!!!
[root@slave1 /]$ lvdisplay --- Logical volume --- LV Path /dev/vgdata/lvolhome LV Name lvolhome VG Name vgdata LV UUID dI2lMQ-sayc-XGlG-xa9I-USfC-97kt-0Kbt6k LV Write Access read/write LV Creation host, time slave1, 2018-04-27 23:23:00 -0700 LV Status available # open 0 LV Size 4.90 GiB Current LE 1255 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0
4.4 Format the disk
[root@slave1 /]$ mkfs.ext4 /dev/sda4 mke2fs 1.41.12 (17-May-2010) /dev/sda4 is apparently in use by the system; will not make a filesystem here!
Error reporting, manual removal of DM management
[root@slave1 /]$ dmsetup status vgdata-lvolhome: 0 10280960 linear [root@slave1 /]$ dmsetup remove_all [root@slave1 /]$ dmsetup status No devices found
Reformat, OK! ! !
[root@slave1 /]$ mkfs.ext4 /dev/sda4 mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 1310720 inodes, 5241540 blocks 262077 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 160 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 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
Remount, no error is reported, mount is successful, disk expansion is successful
[root@slave1 /]$ mount /dev/sda4 /disk4
Before mounting:
[root@slave1 /root]$ df -lh Filesystem Size Used Avail Use% Mounted on /dev/sda2 18G 3.0G 14G 18% / tmpfs 491M 72K 491M 1% /dev/shm /dev/sda1 291M 34M 242M 13% /boot
After mounting:
Filesystem Size Used Avail Use% Mounted on /dev/sda2 18G 3.1G 14G 19% / tmpfs 491M 72K 491M 1% /dev/shm /dev/sda1 291M 34M 242M 13% /boot /dev/sda4 20G 172M 19G 1% /disk4