Results 1 to 1 of 1
Hello Friends ,
Sorry if this might sounds too old , but i `ve been looking round & round desperately trying to find a fix for the mess i`ve made ...
- 10-03-2011 #1Just Joined!
- Join Date
- May 2011
- Posts
- 13
LVM Resize went wrong !
Hello Friends ,
Sorry if this might sounds too old , but i `ve been looking round & round desperately trying to find a fix for the mess i`ve made and i got too confused !
Well let me cut it short :-
i was trying to resize "reduce" my /backup lvm-partition on /dev/mapper/vol_raid-volbackup
to freeup some space for /var on /dev/mapper/vol_raid-volvar
but it all went wrong !
# although i`m aware of the procedure sequence :-
1- boot into single-user mode
2- umount /dev/mapper/vol_raid-volbackup
3- e2fsck -fc /dev/mapper/vol_raid-volbackup
4- resize2fs -f -p /dev/mapper/vol_raid-volbackup 1000G
5- lvresize -L 1T /dev/mapper/vol_raid-volbackup
6- e2fsck -fc /dev/mapper/vol_raid-volbackup
i went for step 5 (lvresize) before step 4 (resize2fs)
now this is what i get when i try any of the following :-
Code:resize2fs -f -p /dev/mapper/vol_raid-volbackup 1000G resize2fs 1.39 (29-May-2006) Resizing the filesystem on /dev/mapper/vol_raid-volbackup to 262144000 (4k) blocks. resize2fs: Can't read an block bitmap while trying to resize /dev/mapper/vol_raid-volbackup
Code:e2fsck -f -p /dev/mapper/vol_raid-volbackup /dev/mapper/vol_raid-volbackup: The filesystem size (according to the superblock) is 473956352 blocks The physical size of the device is 268435456 blocks Either the superblock or the partition table is likely to be corrupt! /dev/mapper/vol_raid-volbackup: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)
PLease Guys Guide me with this , i feel so stupid !Code:fsck /dev/mapper/vol_raid-volbackup fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) The filesystem size (according to the superblock) is 473956352 blocks The physical size of the device is 268435456 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? n /dev/mapper/vol_raid-volbackup contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Error reading block 268435458 (Invalid argument) while doing inode scan. Ignore error<y>? yes Force rewrite<y>? yes Error writing block 268435458 (Invalid argument) while doing inode scan. Ignore error<y>? yes Error reading block 268435459 (Invalid argument) while doing inode scan. Ignore error<y>? yes Force rewrite<y>?
Thank you ..


Reply With Quote