Hey all -- Here's the problem that I'm having at the moment: I created a xen machine that uses an LVM partition as it's root filesystem. Using LVM's snapshot functionality I created multiple LVM snapshot partitions of this master, each of which is assigned as the root filesystem of another xen virtual machine. All seemed fine, until it was necessary to reboot the physical machine on which these LVM volumes exist. Now one of the LVM partitions is a little bit gone. Specifically: - `lvs` shows the partition as present, but INACTIVE - '/dev/dm-X' exists, and by mounting it I can get access to the partition; fdisk on this device checks out fine. - '/dev/mapper/volgroup-logicalvolume' exists, but cannot be mounted. Fdisk on this device fails. - '/dev/volgroup/logicalvolume', which is generally a symlink to /dev/mapper/volgroup-logicalvolume, does not exist at all. The '/dev/volgroup/logicalvolume' syntax is far more convenient than the /dev/dm-X syntax, since the value of X can change across reboots (or when deleting a snapshot and recreating another with the same name, for example). So I'd really like to have that approach functional... `dmesg`, /var/log/messages, etc show nothing useful; no errors or anything else, that I can see... `uname -a` gives this: Linux xenhost0 2.6.16.13-4-xen #1 SMP Wed May 3 04:53:23 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux So, questions: - Any idea what would cause a snapshot to be marked INACTIVE on a reboot? - Any idea why the INACTIVE snapshot would be mountable, when addressed as /dev/dm-X? - Any idea why the /dev/mapper/volgroup-logicalvolume device would no longer be functional? And why the /dev/volgroup/logicalvolume symlink wouldn't have been created? (And, well...is there a better place to ask these questions? I've gotten ot the point that I assume that someone on SLE can answer any question I might have :-)