860
Comment:
|
1266
|
Deletions are marked like this. | Additions are marked like this. |
Line 6: | Line 6: |
* NOTE:201507: Rather look at btrfs, it is reasonably mature, and does most thins lvm is used for. | * NOTE:201507: Rather look at [[linux/btrfs|BTRFS]], it is reasonably mature, and does most thins lvm is used for. |
Line 18: | Line 18: |
vgscan --mknodes (may not be neccessary, but won't hurt) | vgscan --mknodes (may not be necessary, but won't hurt) |
Line 26: | Line 26: |
== 2020 add disk to existing centos Linux == * Start PV /dev/sda2, then using vmware extend disk, using fdisk /dev/sda add additional partition /dev/sda3 * Add /dev/sda3 as PV $ sudo pvcreate /dev/sda3 * Add PV to VG vgextend [vgname] /dev/sda3 $ sudo vgextend vg_<xyz> /dev/sda3 * vgdisplay [vg)<xyz>] * add free space in VG to LV $ sudo lvextend -L+20G /dev/vg_xyz/lv_root |
LVM Linux volume management
NOTE:201507: Rather look at BTRFS, it is reasonably mature, and does most thins lvm is used for.
- All Harddrives(HD's = pv=physicalvolumes) are put into a vg(volume group = 1big virtual hd) and then you partion it into lv's(logical volumes)
Why ?
- LV's can migrate while live - e.g. remove a disk
- LV's can expand while live
Notes
vgchange -a n vgscan --mknodes (may not be necessary, but won't hurt) vgexport -a vgimport -a vgchange -a y That should bring them back to life.
Undo a lvm mistake ball by ball
2020 add disk to existing centos Linux
- Start PV /dev/sda2, then using vmware extend disk, using fdisk /dev/sda add additional partition /dev/sda3
- Add /dev/sda3 as PV $ sudo pvcreate /dev/sda3
Add PV to VG vgextend [vgname] /dev/sda3 $ sudo vgextend vg_<xyz> /dev/sda3
vgdisplay [vg)<xyz>]
- add free space in VG to LV $ sudo lvextend -L+20G /dev/vg_xyz/lv_root