On 8/11/06 12:24 PM, "Greg Freemyer"
All,
I had an air conditioner go out yesterday and a suse 10.1 based fileserver got shutdown non-gracefully.
Today, one of my LVM virtual partitions is not working (Yes, I have a backup from the previous night, but I hope not to need it.)
A quick look at "/dev/<my-lvm-domain>/* shows that one of the links to /dev/mapper/* that should be there is missing. ie. 2 are present and the corresponding filesystems are mounting fine. The 3rd is missing and it obviously will not mount.
The missing link is /dev/<my-lvm-domain>/data
I would simply recreate it, but looking at /dev/mapper I'm surprised to find 2 entries that could be my lvm partition: /dev/mapper/<my-lvm-domain>-data /dev/mapper/<my-lvm-domain>-data-real
Is it safe for me to simply try creating a link for -data then issueing a mount command?
Same symptoms I'm seeing, with a snapshot! If you do a mount on /dev/mapper/<my-lv-domain>-data, does that work? What about the /dev/mapper/<my-lv-domain>-data-real? Does fsck pass on either/both of them, or does it fail to read the filesystem?