...
- Cuando el servidor haya reiniciado, ejecutamos un pvresize a /dev/nvme0n1p2 para para redimensionar el espacio, seguido de un lvextend a vg_nmis-lv_root para extenderlo al 28% y un un lvextend a vg_nmis-var para extenderlo al 72%.
| Code Block |
|---|
[root@nmis9 ~]# pvresize /dev/nvme0n1p2 Physical volume "/dev/nvme0n1p2" changed 1 physical volume(s) resized or updated / 0 physical volume(s) not resized ----- [root@nmis9 ~]# lvextend -l 100%VG28%VG /dev/mapper/rhel-root Reducing 100%VG to remaining free space <297.00 GiB in VG. Size of logical volume rhel/root changed from <17.00 GiB (4351 extents) to <297.00 GiB (76031 extents) Logical volume rhel/root successfully resized.vg_nmis-lv_root o [root@nmis9 ~]# lvextend --size +40G /dev/mapper/vg_nmis-lv_root ----- [root@nmis9 ~]# lvextend -l 72%VG /dev/mapper/vg_nmis-var o [root@nmis9 ~]# lvextend --size +139G /dev/mapper/vg_nmis-var |
- Para finalizar, ejecutamos un fsadm a rhel-root para comprobar el tamaño del sistema de archivos y verificar que todo está correcto.
| Code Block |
|---|
[root@nmis9 ~]# fsadm resize /dev/mapper/vg_nmis-lv_root
[root@nmis9 ~]# fsadm resize /dev/mapper/vg_nmis-var |
| Code Block |
|---|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:0 0 140G 0 disk
└─nvme1n1p1 259:1 0 140G 0 part
└─vg_data-lv_data 253:2 0 140G 0 lvm /data
nvme0n1 259:2 0 140G 0 disk
├─nvme0n1p1 259:3 0 1G 0 part /boot
└─nvme0n1p2 259:4 0 139G 0 part
├─vg_nmis-lv_root 253:0 0 38.9G 0 lvm /
└─vg_nmis-var 253:1 0 100.1G 0 lvm /var |
| Code Block |
|---|
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs 7.7G 0 7.7G 0% /dev/shm
tmpfs 7.7G 25M 7.7G 1% /run
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/mapper/vg_nmis-lv_root 39G 5.5G 31G 15% /
/dev/nvme0n1p1 976M 225M 684M 25% /boot
/dev/mapper/vg_nmis-var 99G 564M 94G 1% /var
/dev/mapper/vg_data-lv_data 138G 1.1G 131G 1% /data
tmpfs 1.6G 0 1.6G 0% /run/user/0 |