LinHES Forums :: View topic - LVM Filesystem Size Problem

...
/dev/sdh15: open failed: no such device or address
Found volume group "vg" using metadata lvm2
/dev/vg: opendir failed: no such file or directory
1 logical volume(s) in volume group "vg" now active
Checking all file systems
fsck 1.36 (05-Feb-2005)
The filesystem size (according to the superblock) is 95942680 blocks. The physical size of the device is 66639872 blocks. Either the superblock or the partition table is likely to be corrupt.
myth: Unexpected inconsistency; Run fsck manually (i.e. without -a or -p options).
fsck failed. Please repair manually.

The filesystem size (according to the superblock) is 95942680 blocks. The physical size of the device is 66639872 blocks. Either the superblock or the partition table is likely to be corrupt. Abort<y>?n
Pass 1 Checking indoes blocks and sizes
Error reading block 66650114(invalid argument) while doing inode scan. Ignore error<y>?

Error reading block 66650114(Invald argument) while reading inode and block bitmaps. Ignore error<y>? yes

Force rewrite<y>?

... +(95879168--95879170) +(95911936--95911938)
Fix<y>? yes

myth: ***** FILE SYSTEM WAS MODIFIED ******
myth 26172/93696 files (23.1% non-contiguous), 24811618/95943680 blocks

Error writing block 95911937(Invalid argument) while writing block bitmaps. Ignore error <y>?

Author:	psicard [ Sun May 21, 2006 10:48 am ]
Post subject:	LVM Filesystem Size Problem
I had a hard drive that was part of an LVM volume group start having problems (probably due to excessive heat). So, I bought a replacement and tried to follow instructions on the Wiki to add a new drive, move everything off the bad drivel, and then remove the bad drive. I say tried because apparently I did something wrong. Now when I boot, I get: Code: ... /dev/sdh15: open failed: no such device or address Found volume group "vg" using metadata lvm2 /dev/vg: opendir failed: no such file or directory 1 logical volume(s) in volume group "vg" now active Checking all file systems fsck 1.36 (05-Feb-2005) The filesystem size (according to the superblock) is 95942680 blocks. The physical size of the device is 66639872 blocks. Either the superblock or the partition table is likely to be corrupt. myth: Unexpected inconsistency; Run fsck manually (i.e. without -a or -p options). fsck failed. Please repair manually. If I try to run fsck, I get: Code: The filesystem size (according to the superblock) is 95942680 blocks. The physical size of the device is 66639872 blocks. Either the superblock or the partition table is likely to be corrupt. Abort<y>?n Pass 1 Checking indoes blocks and sizes Error reading block 66650114(invalid argument) while doing inode scan. Ignore error<y>? At this point, I I try no, fsck aborts after 2 no's. If I try yes, I get: Code: Force rewrite<y>? And then I get (literally) hundreds of similar questions as it goes through the "missing" blocks. Then after Pass 5, I get hundreds of questions again: Code: Error reading block 66650114(Invald argument) while reading inode and block bitmaps. Ignore error<y>? yes Force rewrite<y>? Then lots of number pairs fill the screen: Code: ... +(95879168--95879170) +(95911936--95911938) Fix<y>? yes myth: *** FILE SYSTEM WAS MODIFIED ** myth 26172/93696 files (23.1% non-contiguous), 24811618/95943680 blocks Error writing block 95911937(Invalid argument) while writing block bitmaps. Ignore error <y>? If I "yes" everything, I eventually get to the shell prompt and there doesn't seem to be any change. So then I tried: Code: resizefs -f /dev/vg/myth 66639872 and got: Code:** Please run 'e2fsck -f /dev/vg/myth' first. I've looked through the LVM HOWTO pages (http://www.tldp.org/HOWTO/LVM-HOWTO/) and googled trying to find what else I can try (except reformatting and losing everything on the volume group) with no luck. That may be too much info, but better too much than not enough... Anyone have any suggestions?

Author:	cesman [ Sun May 21, 2006 10:13 pm ]
Post subject:
Which fs (etx3, xfs, etc) did you use to format /dev/vg/myth? Depending on the fs, you cann resize it...

Author:	psicard [ Tue May 23, 2006 12:03 pm ]
Post subject:
It's ext3. Sorry- I wasn't clear about this in my original post... I tried Code: resize2fs -f /dev/vg/myth 66639872 and got Code: Please run 'e2fsck -f /dev/vg/myth' first. After getting through e2fsck (as described in my original post), I tried resize2fs again and got the same response.

LinHES Forums http://forum.linhes.org/

LVM Filesystem Size Problem http://forum.linhes.org/viewtopic.php?f=5&t=10136	Page 1 of 1

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/