LVMextend vm results in kernal panic

O

offerlam

Renowned Member
Dec 30, 2012
226
2
83
Denmark
Hi all,

I have been struggeling with this issue for a long time now.
I haven't posted it here becuase I considered the issue being ubuntu os related.
But looking over some post something tells me it may be a vm proxmox issue.

The issue is that i have a disc that is 600gb large.
I have a LVM on this disc that is 100Gb large. It has run out of disc space.

I have tried PVresize bevore Lvmextend. I have tried lvmextend. I have tried lvmextend with -r to the lvm resize the filesystem but that didn't work. And when i run resize2fs it work.

When i run these commands i do see that my LVM volume is being expanded to 600Gb.

But when i boot the system it kernal panics.

here is some info to go by

Code: 
Disk /dev/sda: 600 GiB, 644245094400 bytes, 1258291200 sectors
Disk model: QEMU HARDDISK  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6E326018-BFB7-45EF-BBF4-A7BBE46C321F

Device       Start        End    Sectors  Size Type
/dev/sda1     2048       4095       2048    1M BIOS boot
/dev/sda2     4096    4198399    4194304    2G Linux filesystem
/dev/sda3  4198400 1258289151 1254090752  598G Linux filesystem

and perhaps df -h
Code: 
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              743M  1.1M  742M   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   98G   93G     0 100% /
tmpfs                              3.7G  4.0K  3.7G   1% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                              3.7G   64K  3.7G   1% /tmp
/dev/sda2                          2.0G  239M  1.6G  14% /boot
tmpfs                              1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                              1.0M     0  1.0M   0% /run/credentials/systemd-networkd.service
tmpfs                              1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs                              1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs                              743M   16K  743M   1% /run/user/1000

lsblk
Code: 
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda                         8:0    0  600G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    2G  0 part /boot
└─sda3                      8:3    0  598G  0 part
  └─ubuntu--vg-ubuntu--lv 252:0    0  100G  0 lvm  /
sr0                        11:0    1 1024M  0 rom

I need help
 
Assuming you have (already) used all the correct commands - I suspect the issue is being caused by running the commands with the disk/partition/LVM online coupled with the fact that it appears that the LVM is already full, as shown here:
offerlam said:
/dev/mapper/ubuntu--vg-ubuntu--lv 98G 93G 0 100% /
Click to expand...

To deal with this, I would do the following:

1. Make sure you have complete & restorable backup/s of the VM.
2. Attach another ISO with some Linux live media (GParted etc.) to the VM & set it as the first boot device. Boot the VM.
3. Run the various disk/partition/LVM commands on the /dev/sda disk FROM the live-media environment.
4. Shutdown & remove that above ISO from the VM (2 above). Make sure the VM is now set to boot from the original disk.
5. Boot the VM & test.

Good luck.
 
Hi all
Thanks for the suggestions.
I guess its not a proxmox problem and i have chosen to just reinstall the server and make sure the LVM uses the entire disk this time.
thanks :)
 
You must log in or register to reply here.
Top Bottom