Okay. I've been having great trouble with LVM.
In a previous post, I had discussed my difficulties using LVM under SuSE 9.0 with a 2.4-based kernel, but now I'm tring to get my Debian based 2.6 kernel back on track.
I've been trying to figure out how to apply the device-mapper patch to my kernel for snapshot and pvmove capabilities, but before knowing that I needed to patch my kernel, I tried making a snapshot.
Since then, I'm not been able to properly mount one of my LVM partitions. The one in question is the Domino partition listed below:
dehuszar@dblstitch:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / reiserfs defaults 0 1
/dev/mapper/Domino-Domino /domino xfs defaults 0 2
/dev/mapper/Home-Home /home reiserfs defaults 0 2
/dev/hda7 /tmp reiserfs defaults 0 2
/dev/hda5 /usr reiserfs defaults 0 2
/dev/hda6 /var reiserfs defaults 0 2
/dev/hda4 none swap sw 0 0
/dev/hdb /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/hdd /media/cdrom1 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
dblstitch:/home/dehuszar# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 957M 127M 831M 14% /
tmpfs 253M 0 253M 0% /dev/shm
/dev/mapper/Home-Home
70G 3.5G 67G 5% /home
/dev/hda7 957M 33M 925M 4% /tmp
/dev/hda5 4.7G 371M 4.3G 8% /usr
/dev/hda6 2.8G 254M 2.6G 9% /var
auto/dev/Domino/Domino
957M 127M 831M 14% /domino
dblstitch:/home/dehuszar# lvscan
ACTIVE '/dev/Home/Home' [70.00 GB] inherit
ACTIVE '/dev/Domino/Domino' [20.00 GB] inherit
dblstitch:/home/dehuszar#
dblstitch:/home/dehuszar# ACTIVE '/dev/Home/Home' [70.00 GB] inherit
bash: ACTIVE: command not found
dblstitch:/home/dehuszar# ACTIVE '/dev/Domino/Domino' [20.00 GB] inherit
bash: ACTIVE: command not found
dblstitch:/home/dehuszar#
Should I be concerned by the auto/dev/Domino/Domino listing in the df results? and why does it match my root partition's size and usage info? It' won't mount to /domino/ where I originally told it to. It now gives me a "can't read superblock" error.
This used to work, and I'd really like it to work again without icing the partition and reformatting.
Any ideas? Do you need more info?
Thanks in advance,
Sam
