Docker MySQL container report too many connections triggered by LIUNX disk expansion operation

• Symptoms every time you remove the MySQL container restart no two minutes and report the wrong title
• df-h command to view the application of each mount space discovery Root home var three files directory the space is full.
• Baidu on the Internet a bit LIUNX disk expansion operation, the fdisk-l command finally found that the machine has a piece of 270 of the disk is not mounted
• The PV is created and the disk/dev/xvdb is created as a system PV with the Pvcreate command

  [[email protected] home] # Pvcreate/dev/xvdb " /dev/xvdb " successfully created

• The
• adds pv/dev/xvdb to the volume group Volgroup. The disk has been added to the Volgroup, and the volume group has increased its space by 270G. Use the command vgextend volgroup/dev/xvdb

   [[email protected] Home]#   vgextend volgroup/dev/xvdb  Volume group  " volgroup  "   successfully Extended[root  @localhost home]#   VGS    VG #  PV #LV #SN Attr vsize vfree  VolGroup 2 3 0 wz--n-265.50g 0 

• To/Add 10G of space. Using the command lvextend-l +10g/dev/mapper/volgroup-lv_root

  [[email protected] home] # lvextend-l +10g  /dev/mapper/volgroup-lv_root  Size of logical volume Volgroup/lv_root changed from 50.98 Gib (13050 extents) to 55.98 Gib (14330 extents ).  Logical Volume Lv_root successfully resized

• The logical volume extension does not take effect immediately, and you need to reload the logical volume with the "RESIZE2FS" command. Use the command resize2fs/dev/volgroup/lv_root. But it did not succeed.
• Final Xfs_growfs/dev/volgroup/lv_root command solves the above problem

Docker MySQL container report too many connections triggered by LIUNX disk expansion operation