Hot answers tagged lvm
You'd only ever shoot yourself in the foot if you wanted to rename the volume group or logical volume later....(lvrename or vgrename). Forgetting whatever reason you renamed the vg or lv, the action would screw up your mounts and exports. LVUUID remains persistent through vg and lv rename commands. It may be good to use UUID for this reason alone, ...
An LVM snapshot works by keeping a list of changed blocks, and their contents, in the snapshot volume, while passing all requests to read unchanged data down to the underlying block device. All of this intelligence is built into LVM, in the kernel, and mount has no knowledge of it. As far as anything in userspace is concerned, there are two block devices ...
Snapshots are part of the LVM subsystem, the data blocks that are an abstraction layer underneath the file system. A snap-shot is a full copy of the original volume and will therefore also be the same size when you mount it. Both will be 1 GB. Except for the fact that a snapshot does some trickery so you don't actually have to fully copy that whole 1 GB. ...
You could try with <target dev='sda' bus='scsi'/> (removing the controller reference) and see if the disk appears during the installation. The best configuration would be <target dev='vda' bus='virtio'/>, but for that you would need the virtio drivers from Fedora; see also http://serverfault.com/a/650681/100793 .
As requested, now as an answer: A wild guess is that the RAID sda/sdb3 had failed a long time ago, running only on sdb. Now that sdb has failed, perhaps it came back online with only sda?
Only top voted, non community-wiki answers of a minimum length are eligible