![]() Size of logical volume rhel/root changed from <47.00 GiB (12031 extents) to <77.00 GiB (19711 extents). # lvresize -l +100%FREE /dev/mapper/rhel-root $ df -hįilesystem Size Used Avail Use% Mounted on dev/mapper/fedora-root 228G 2.3G 226G 2% /Īfter gparted, # xfs_growfs /dev/mapper/rhel-root did the trick on a living system. ![]() Realtime =none extsz=4096 blocks=0, rtextents=0ĭata blocks changed from 3932160 to 59757568ħ) #df -h Filesystem Size Used Avail Use% Mounted on Log =internal bsize=4096 blocks=2560, version=2 Naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Logical volume fedora/root successfully resized.Ħ) # xfs_growfs /dev/mapper/fedora-root meta-data=/dev/mapper/fedora-root isize=512 agcount=4, agsize=983040 blksĭata = bsize=4096 blocks=3932160, imaxpct=25 VG UUID 9htamV-DveQ-Jiht-Yfth-OZp7-XUDC-tWh5Lvģ) # lvextend -l +100%FREE /dev/mapper/fedora-root Size of logical volume fedora/root changed from 15.00 GiB (3840 extents) to 227.96 GiB (58357 extents). I've probably done something stupid, so any help would be greatly appreciated!Īfter reading about LVM and being familiar with PV -> VG -> LV, this works for me :Ġ) #df -h Filesystem Size Used Avail Use% Mounted on LV UUID ugCOcT-sTDK-M8EV-3InM-hjIg-2nwS-KeAOnq LV Creation host, time localhost, 08:28:42 +0100 LV UUID KyokrR-NGsp-6jVA-P92S-QE3X-hvdp-WAeACd VG UUID FD7k1M-koJt-2veW-sizL-Srsq-Y6zt-GcCfz6 PV UUID p0IClg-5mrh-5WlL-eJ1v-t6Tm-flVJ-gsJOK6 ![]() I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Hopefully some of the following will shed some light.ĭisk /dev/xvda: 32.2 GB, 32212254720 bytes, 62914560 sectors Once I tried to use resize2fs, using both methods as above, I received the exact same error. Again everything worked fine up to this point. I have also tried deleting an existing partition (using fdisk) and recreating it with a larger end block, then resizing the physical volume using lvm pvresize, followed by a resize of the logical volume using lvm lvresize. Resize worked fine for the logical volume using lvextend, but it failed at resize2fs. I have tried adding a new partition (using fdisk) and using vgextend to extend the volume group, then resizing. Resize2fs: Bad magic number in super-block while trying to open /dev/mapper/centos-rootĬouldn't find valid filesystem superblock. I am trying to resize a logical volume on CentOS7 but am running into the following error: resize2fs 1.42.9 (2)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |