On Wed, Feb 18, 2015 at 10:18 AM, Richard W.M. Jones
<rjones@redhat.com> wrote:
On Wed, Feb 18, 2015 at 10:07:20AM -0500, Leonard Basuino wrote:
> > ><rescue> e2fsck -n /dev/sda1
> e2fsck 1.42.9 (28-Dec-2013)
> The filesystem size (according to the superblock) is 104388 blocks
> The physical size of the device is 103408 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort? no
>
> /boot contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> /boot: 36/26104 files (2.8% non contiguous), 12201/104388 blocks
I would say this is (fairly) conclusive proof that the filesystem is
really truncated, and RHEL 6 is just ignoring that hard fact. Note
that the code paths used by ext4 kernel and e2fsck (ie. e2fsprogs) are
quite different, and both think the filesystem is longer than the
containing device.
Sorry :-(
No need to be sorry ... you have put me on a promising path ...
I was able to mount it after resizing the filesystem ...
within virt-rescue ...
><rescue> resize2fs -f /dev/sda1
then I was able to mount it with ...
guestmount -a <image> -m /dev/sda1 <mount point>
Not ideal for my needs, but work in progress.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v