> I strongly suspect that this is not an ext2/3/4 filesystem....
The recovered /etc/fstab mounts it as an ext3 filesystem:
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/teramooch-root / ext3
relatime,errors=remount-ro 0 1
UUID=20be44f0-4da3-439e-ae4e-cc4e08cc8e37 /boot ext2
relatime 0 2
UUID=B627-AFF0 /fat32 vfat utf8,umask=007,gid=46 0 1
/dev/mapper/teramooch-home /home ext3 relatime 0 2
/dev/mapper/teramooch-opt /opt ext3 relatime 0 2
/dev/mapper/teramooch-srv /srv ext3
relatime,acl,user_xattr 0 2
/dev/mapper/teramooch-tmp /tmp ext3 relatime 0 2
/dev/mapper/teramooch-usr /usr ext3 relatime 0 2
/dev/mapper/teramooch-var /var ext3 relatime 0 2
/dev/mapper/teramooch-backupduffycapemay
/srv/samba/mac_backups/duffycapemay ext3 relatime
0 2
UUID=7fb288ca-400a-415a-97b7-35ceccddeb0f none swap sw
0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
> It seems strange that this LV would be totally corrupted while the other
> LV's are perfect, but that is another possibility (however unlikely). Again,
> looking at the raw drive should show some file contents (if you look through
> enough of it), and this might also provide some help in working out what the
> problem is. I once assembled my raid0 (striping) in the wrong order, and
> looking at the individual member drives raw contents helped me work out the
> correct order.
>
> I hope the above helps. For now, it sounds like your FS format is not
> ext2/3/4 based. Maybe another one of the popular linux formats?
The /dev/mapper/teramooch-srv logical volume does represent a huge
majority of the disk space.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
