I have spent some time on this and tested all permutations. My evaluation is that
eudev-3.1.1 is the agency responsible for breaking the mounting of an LVM snapshot, to wit:
Code:
lvcreate --snapshot --name lfs3snap --size 8G vg01/lfs3
Logical volume "lfs3snap" created.
mount /dev/mapper/vg01-lfs3snap /mnt/other/
mount: /dev/mapper/vg01-lfs3-real is already mounted or /mnt/other busy
The mount error only occurs with
eudev-3.1.1. Rolling back to the prior
eudev-3.1 revision resolves the problem. I'm not sure how widely used LVM is in the LFS world but this is a heads up for those who may run across this.
Given that using the SVN branch of LFS/BLFS yields a rapidly moving target, it took quite some to isolate the possible software packages involved. For the record, LVM is 2.02.120 in use here, that's the latest.