CentOS Fails To Book After lvextend
 

Hello,

I currently run a server that has CentOs 64 bit installed on it. We received a notification from WHM stating that one of our partions was at 89% full.To prevent it from filling up, I lvextend -L +16G /dev/mapper/vg_mhhub-lv_home . It extended the drive and when I did df -h, it only showed 34% used. After that, we rebooted and now the server will not start. It is giving errors stating that the filesystem size (according to the superblock) is 228761680 blocks. The physical size of the device is 207003648. Either the superblock or the partion table is likely to be corrupt.

The server has been offline for several days now as I have been trying all types of stuff found on this forum and other websites trying to resolve. When I run fsck manually as it states, it gives errors such as Error reaading block 207093760 (invalid argument) while reading inode and block bitmaps. It asks if I want to ignore and I always so no (even though it repeats this message over and over again) and exit the shell and the server tries to rebook and gives the same thing. Any help would be greatly appreciated. Also, it states fsck:ext4: Cant read an block bitap while retrying to read bitmaps for /dev/mapper/vg_mapper/vg_mhhub-lv_home.

df outputs as follows:

You say you _only_ did an lvextend.

Usually after an lvextend (which only extends the logical volume, not the filesystem) you have to do a resize2fs to extend the filesystem to the new lv size.

Don't know if its too late now, but I'd say try this:

resize2fs /dev/mapper/vg_mhhub-lv_home

Thanks for the reply. When I run that command it tells me to run e2fsck -f /dev/mapper/vg_mhhub-lv_home first. When I run that command, it says the same thing about the super block or portion table being corrupt and asks me if I want to abort. I press no and it runs through 5 checks and then it says error reading block 207093760 (invalid argument) while reading inode and block bitmaps. In gore error?. If I say no it says can't read an block bitmap while retrying to read bitmaps and then it aborts. If I press yes to ignore, I eventually end up at the same error

I find it hard to believe all the non-tmpfs filesystems are exactly the same size and used. Where did you get that "df" listing from - does the server drop to rescue mode on boot ?.
That's a worry - we woud need to know precisely what you did, and in what order, to have any chance of making an informed suggestion.