Cant expand root partition LVM |resize2fs: Operation not permitted While trying to add group #512
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cant expand root partition LVM |resize2fs: Operation not permitted While trying to add group #512
Hello Folks .
i have cento 6 64 bits over LVM partition .
i cant expand my root partition .
the LV size on root partition is
LV Size 750.00 GiB
but in Df -h its on 64 G
##############################################
here is info
Quote:
#################
[root@R122020 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_r122020-lv_root
63G 15G 46G 25% /
tmpfs 7.9G 2.0M 7.9G 1% /dev/shm
/dev/sda1 477M 79M 369M 18% /boot
shm 7.9G 2.0M 7.9G 1% /dev/shm
[root@R122020 ~]# resize2fs /dev/mapper/vg_r122020-lv_root
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/mapper/vg_r122020-lv_root is mounted on /; on-line resizing required
old desc_blocks = 4, new_desc_blocks = 47
Performing an on-line resize of /dev/mapper/vg_r122020-lv_root to 196608000 (4k) blocks.
resize2fs: Operation not permitted While trying to add group #512
[root@R122020 ~]#
###############################
in kernel i have
Jul 15 02:30:26 R122020 kernel: EXT4-fs warning (device dm-0): ext4_group_add:1605: No reserved GDT blocks, can't resize
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
here is more info
[root@R122020 ~]# lvdisplay
--- Logical volume ---
LV Path /dev/vg_r122020/lv_root
LV Name lv_root
VG Name vg_r122020
LV UUID xtvyvf-XLLX-XhsI-XAU5-ari7-g1fH-Kpc2IR
LV Write Access read/write
LV Creation host, time R122020, 2018-05-18 10:01:09 -0400
LV Status available
# open 1
LV Size 750.00 GiB
Current LE 192000
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/vg_r122020/lv_home
LV Name lv_home
VG Name vg_r122020
LV UUID bCBRN8-aQtb-4KhF-kuZG-AKtb-67nO-tHj94s
LV Write Access read/write
LV Creation host, time R122020, 2018-05-18 10:01:18 -0400
LV Status available
# open 0
LV Size 23.22 GiB
Current LE 5945
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Path /dev/vg_r122020/lv_swap
LV Name lv_swap
VG Name vg_r122020
LV UUID u1oI21-3Xdf-FIq5-d7j7-Vd5P-uagO-zbzRcl
LV Write Access read/write
LV Creation host, time R122020, 2018-05-18 10:03:45 -0400
LV Status available
# open 2
LV Size 7.80 GiB
Current LE 1996
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
You have mail in /var/spool/mail/root
[root@R122020 ~]# vgdisplay
--- Volume group ---
VG Name vg_r122020
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 931.02 GiB
PE Size 4.00 MiB
Total PE 238341
Alloc PE / Size 199941 / 781.02 GiB
Free PE / Size 38400 / 150.00 GiB
VG UUID cAOabA-bHye-UVSD-RNyK-E1vc-o1IZ-rcZZS0
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 121602 976248832 8e Linux LVM
Next time, please put code tags around your code. The way it looks right now, it is very hard to read.
The error message
Code:
No reserved GDT blocks, can't resize
indicates that the filesystem doesn't have the online-resize feature set. See also https://bugzilla.redhat.com/show_bug.cgi?id=208322 and the many other results when searching the internet for the error string.
Another possibility is that you ran out of GDT blocks (I leave it as an exercise to the reader to find out what that is), but according to Theodore Ts'o, the creator of ext4 himself, this is unlikely.
I don't think online-resizing can be enabled retroactively, but perhaps it is possible? If I am right, your only solution is probably backing up root, creating a larger filesystem (with online-resizing) and restoring the backup. Or remove some files.
Last edited by berndbausch; 07-15-2019 at 03:48 AM.
Each of the backup super blocks contains a complete copy of the GDT and needs to have reserved space to allow the GDT to grow. The mkfs.ext4 in CentOS 6 reserves enough GDT blocks to enlarge a filesystem to 1024 times its original size. If you have somehow created a filesystem without reserved GDT blocks, or are trying to enlarge the filesystem to more than 1024 times its originally created size, then there is nothing you can do other than creating a brand new filesystem and restoring your data to it.
Does "dumpe2fs /dev/mapper/vg_r122020-lv_root | grep -E 'GDT|superblock" show any reserved GDT blocks? It seems a bit odd that the first reported error would be at group #512.
[root@R122020 X5]# dumpe2fs /dev/mapper/vg_r122020-lv_root | grep -E 'GDT|superblock'
dumpe2fs 1.41.12 (17-May-2010)
Reserved GDT blocks: 1020
Primary superblock at 0, Group descriptors at 1-4
Reserved GDT blocks at 5-1024
Backup superblock at 32768, Group descriptors at 32769-32772
Reserved GDT blocks at 32773-33792
Backup superblock at 98304, Group descriptors at 98305-98308
Reserved GDT blocks at 98309-99328
Backup superblock at 163840, Group descriptors at 163841-163844
Reserved GDT blocks at 163845-164864
Backup superblock at 229376, Group descriptors at 229377-229380
Reserved GDT blocks at 229381-230400
Backup superblock at 294912, Group descriptors at 294913-294916
Reserved GDT blocks at 294917-295936
Backup superblock at 819200, Group descriptors at 819201-819204
Reserved GDT blocks at 819205-820224
Backup superblock at 884736, Group descriptors at 884737-884740
Reserved GDT blocks at 884741-885760
Backup superblock at 1605632, Group descriptors at 1605633-1605636
Reserved GDT blocks at 1605637-1606656
Backup superblock at 2654208, Group descriptors at 2654209-2654212
Reserved GDT blocks at 2654213-2655232
Backup superblock at 4096000, Group descriptors at 4096001-4096004
Reserved GDT blocks at 4096005-4097024
Backup superblock at 7962624, Group descriptors at 7962625-7962628
Reserved GDT blocks at 7962629-7963648
Backup superblock at 11239424, Group descriptors at 11239425-11239428
Reserved GDT blocks at 11239429-11240448
[root@R122020 X5]#
I just don't see anything wrong with either the filesystem or the LVM structure. The filesystem is currently using just 4 of the 1024 GDT blocks, and resize2fs reports that only 47 are needed for the new size. Perhaps it's time for a reboot with a forced fsck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
