Mesed up with Linux partition resizing...
Hi,
I messed up today with production server on Linux Ubuntu 10.04 LTS. I wanted to extend LVM partition on Virtual Linux server (ESX 5.0), something came out during my work and I I forgot to make snapshot!
What I did already?
First, I shut down Linux server (with intention to make snapshot...but I forgot), added some 35GB to virtual DISK space in ESX, and powered up machine.
This is BEFORE any changes:
Then my situation was as follows:
MISTAKE!
So I messed up with the following commands, which I need to UNDO somehow:
As you see, I extended with WRONG volume, which is only 8MB in size, instead of 35GB.
I need to revert these TWLO last actions to get partition tables fixed first.
I messed up today with production server on Linux Ubuntu 10.04 LTS. I wanted to extend LVM partition on Virtual Linux server (ESX 5.0), something came out during my work and I I forgot to make snapshot!
What I did already?
First, I shut down Linux server (with intention to make snapshot...but I forgot), added some 35GB to virtual DISK space in ESX, and powered up machine.
This is BEFORE any changes:
root@enginex:/home/labsy# fdisk -l
Disk /dev/sda: 80.5 GB, 80530636800 bytes
255 heads, 63 sectors/track, 9790 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f1f94
Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 248832 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 32 2611 20719617 5 Extended
/dev/sda3 2611 5221 20967186+ 83 Linux
/dev/sda5 32 2611 20719616 8e Linux LVMroot@enginex:/home/labsy# fdisk /dev/sda
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): p
Disk /dev/sda: 80.5 GB, 80530636800 bytes
255 heads, 63 sectors/track, 9790 cylinders, total 157286400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f1f94
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 41940991 20719617 5 Extended
/dev/sda3 41940992 83875364 20967186+ 83 Linux
/dev/sda5 501760 41940991 20719616 8e Linux LVM
Command (m for help): n
Command action
l logical (5 or over)
p primary partition (1-4)
p
Selected partition 4
First sector (499712-157286399, default 499712):
Using default value 499712
Last sector, +sectors or +size{K,M,G} (499712-501757, default 501757):
Using default value 501757
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.Then my situation was as follows:
root@enginex:/home/labsy# fdisk -l
Disk /dev/sda: 80.5 GB, 80530636800 bytes
255 heads, 63 sectors/track, 9790 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f1f94
Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 248832 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 32 2611 20719617 5 Extended
/dev/sda3 2611 5221 20967186+ 83 Linux
/dev/sda4 32 32 1023 83 Linux
Partition 4 does not end on cylinder boundary.
/dev/sda5 32 2611 20719616 8e Linux LVM
Partition table entries are not in disk orderMISTAKE!
So I messed up with the following commands, which I need to UNDO somehow:
root@enginex:/home/labsy# pvcreate /dev/sda4
Physical volume "/dev/sda4" successfully created
root@enginex:/home/labsy# vgdisplay | grep "Name"
VG Name enginexroot@enginex:/home/labsy# vgextend enginex /dev/sda4
Volume group "enginex" successfully extended
root@enginex:/home/labsy# vgdisplay enginex | grep "Free"
Free PE / Size 2 / 8.00 MiBAs you see, I extended with WRONG volume, which is only 8MB in size, instead of 35GB.
I need to revert these TWLO last actions to get partition tables fixed first.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes,
to confirm:
1.) Everything is still working fine.
2.) I created partition, but partition tables did not reflect the correct layout.
3.) I should've fixed the partition tables BEFORE I created PV from this partition, so I stuck by extending VG with 8MB of "some" space, instead of wanted 35GB
Why remove?
Well, first of all, I do not know, which space I added. I obviously did something I do not understand, and would like to get back to the path I know :)
@Arnold:
Due to a simple fact - I am copy-paste google Linux guy, especially here at LVM. I understand Windows partition layout perfectly, but I am totally lost within these LVM partitions, volumes, physical etc.
For me, it is that BEFORE I have xy space for files, then do some mambo jambo in Linux console...and voila, I have more space available :)
to confirm:
1.) Everything is still working fine.
2.) I created partition, but partition tables did not reflect the correct layout.
3.) I should've fixed the partition tables BEFORE I created PV from this partition, so I stuck by extending VG with 8MB of "some" space, instead of wanted 35GB
Why remove?
Well, first of all, I do not know, which space I added. I obviously did something I do not understand, and would like to get back to the path I know :)
@Arnold:
Due to a simple fact - I am copy-paste google Linux guy, especially here at LVM. I understand Windows partition layout perfectly, but I am totally lost within these LVM partitions, volumes, physical etc.
For me, it is that BEFORE I have xy space for files, then do some mambo jambo in Linux console...and voila, I have more space available :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanx Arnold.
I've been following this tutorial, which I once made after playing a lot with different methods of LVM extending: http://www.zimbra.com/forums/administrators/55983-create-new-partition-extend-existing-one.html#post243191
I guess it is the 2nd method you mentioned.
So, I went with SNAPSHOT first, then reduced VG and removed PV. Then I removed partition and after reboot recreated it back.
This time it settled down correctly and partition table correctly represented actual layout.
Then followed those commands:
I expected FSCK to be forced upon reboot to check superblocks...but that did not happen. Weird. Just in case I forced fsck upon reboot, but it did only check /dev/sda1 and /dev/sda2
Would it be fine to force also /dev/sda3 and /dev/sda4 to be checked?
If yes, how? :)
I've been following this tutorial, which I once made after playing a lot with different methods of LVM extending: http://www.zimbra.com/forums/administrators/55983-create-new-partition-extend-existing-one.html#post243191
I guess it is the 2nd method you mentioned.
So, I went with SNAPSHOT first, then reduced VG and removed PV. Then I removed partition and after reboot recreated it back.
This time it settled down correctly and partition table correctly represented actual layout.
Then followed those commands:
pvcreate /dev/sda4
vgextend enginex /dev/sda4
vgdisplay enginex | grep "Free"
lvdisplay | grep "Name"
lvextend -L+35G /dev/enginex/root
resize2fs /dev/enginex/rootI expected FSCK to be forced upon reboot to check superblocks...but that did not happen. Weird. Just in case I forced fsck upon reboot, but it did only check /dev/sda1 and /dev/sda2
touch /forcefsckWould it be fine to force also /dev/sda3 and /dev/sda4 to be checked?
If yes, how? :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hmmm...not like that "none":
root@enginex:/home/labsy# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/enginex-root
76257288 25076440 47326448 35% /
none 3059172 184 3058988 1% /dev
none 3064048 0 3064048 0% /dev/shm
none 3064048 76 3063972 1% /var/run
none 3064048 0 3064048 0% /var/lock
none 3064048 0 3064048 0% /lib/init/rw
/dev/sda1 233191 20152 200598 10% /bootroot@enginex:/home/labsy# fsck /dev/mapper/enginex-root
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
/dev/mapper/enginex-root is mounted.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue (y/n)? no
check aborted.
All those referenced as none are fine.
ASKER
Thank you all!
Not sure why did not add a send drive instead of trying to resize the existing one..