0

When I installed xenserver 7, It asked me if I want thick or thin provisioning. Thinking this is a production server I must have chosen EXT because I had problems with LVM before with balooning of disk space (once areas have cleared up). Not to mention plenty of boched moves of the server which left a ghosted disk space. I have 3 local storage repositories that are apperently linked to the xenserver and I cannot delete. Through the progession of time, plenty of things were deleted and reinstalled with the drives being expanded and deleted. Currently the harddisk SR on one of the servers is showing 280GB (I expanded it) and the drive on the system is only a 120GB bird. IT was installed incorrectly Because SDA2 is 120GB with 2 drives inbetween. This is the reading of fdisk

Disk /dev/xvda: 280 GiB, 300647710720 bytes, 587202560 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

Disklabel type: dos

Disk identifier: 0x00091115

Device Boot Start End Sectors Size Id Type

/dev/xvda1 2048 499711 497664 243M 83 Linux

/dev/xvda2 501758 251656191 251154434 119.8G 5 Extended

/dev/xvda3 251656192 419430399 167774208 80G 83 Linux

/dev/xvda4 419430400 461373439 41943040 20G 83 Linux

/dev/xvda5 501760 251656191 251154432 119.8G 8e Linux LVM

Partition table entries are not in disk order.

The drive xvda was expanded I deleted the partition and recreated it and expanded the root drive afterwards. Running out of space again I repeated the process again (I expanded it in xenserver and then within the server) Now I have no way to expand the root drive anymore and if it fills up beyond a certain point the entire xenserver crashes with input/output errors from drive#1 (I have 3)

As you can tell these numbers don't add up to 280GB. Im going to reinstall it I just wanted to know how to install this properly Like should I use EXT and then LVM in the servers or LVM for xenserver and then EXT in the servers

0 Answers0