On the other hand, if you try to share system files between two different systems, you'll probably run into some interesting problems we've never seen before. But that would happen with or without lvm.

It seems that what I was specifically interested, i.e. sharing a logical volume between linux instances in a multi-boot arrangement in exactly the same way as a normal partition, hopping between instances as the mood or need dictates, is something that our community here has no experience of.

@fsmithred and @rolfie, you seem to be describing doing it once or twice and getting away with it, without catastrophe.
That is encouraging, so thanks for that. However, I would also have been interested to hear from people who do it regularly, as part of their standard operating procedure, but it seems that we don't do that sort of thing here.

It could be that the idea is so ridiculous that it is not discussed, or is so commonplace that it is quite unremarkable.
If I ever get around to the experiment, I should probably start off with data I to which I am not too attached.

Interesting, thanks. Are these 'parts' logical volumes?

In my case, no. I have 3 encrypted partitions for the fixed data, volatile Beowulf and volatile Chimaera.

The main system is an encrypted LVM for / and swap.

As fsmithred I have opened LVM shares to fix problems with live systems like Knoppix or the rescue mode of a boot medium often enough to say that I never had any issues.

rolfie

I've also mounted lvm from another installation on a different hard drive in the same computer. It works the same way.

A few extra commands. (Leave out the cryptsetup lines if your lvm is not encrypted.)

___ MOUNT/UNMOUNT ENCRYPTED LVM ___

sudo cryptsetup luksOpen /dev/sdxY label  # then run lvdisplay to get the vg name and lv name
sudo vgchange -a y <volume_group_name> 
mount /dev/mapper/<vg_name-lv_name>  <mountpoint> 

umount <mountpoint>
sudo vgchange -a n <volume_group_name>
sudo cryptsetup luksClose label

Can anyone help with that?

A howto on keeping the configs separate on a shared home would probably be useful for a lot of people.

So there is an lv with "office data" which is mounted by a Beowulf LVM instance when Beowulf is running, and by the Chimaera LVM instance when Chimaera is running? This seems to be similar to what I am hoping to do. For how long has this polyamorous arrangement been on the go without crashing&burning? (No H8, Love is Love, etc)

Splitting /home into generic/sharable and instance-specific seems like it's worth a separate tutorial(hint, hint)? Or maybe you could link to the guides/tutorials you followed?

I have split my /home for my multiboot setup with Beowulf and Chimaera into a partition that holds all office data like pictures, LO files etc, and a distribution specific part that holds all the hidden config and cache files. The office share is linked into the distribution specific part during boot.

rolfie

I  understand that sharing such system-customised partitions as /boot or /home might cause confusion, but have on several occasions shared "data" partitions between linux instances (even ones that are running simultaneously, usually via NFS.) I have also served LVM LVs via NFS. Is native LVM different in this regard? Is there more of a risk of data corruption ?
Are there risks, gotchas, implications to consider?

For example, consider I set up:

Instance01....PV01_on_Inst01....VG01_on_Inst01....LV01_in_VG01_on_Inst01 

Now on the same hardware. I set up the option to boot into another instance:

Instance02....PV01_on_Inst02....VG01_on_Inst02....LV01_in_VG01_on_Inst02

In this case "LV01_in_VG01_on_Inst01"  and "LV01_in_VG01_on_Inst02"  actually contain the same data, because they are the same "logical volume"/"partition"/thing.

Implications, risks, gotchas? Is it possible that this might actually be safe ONLY if the sharing instances never exist at the same time? If so, it's OK in a multi-boot setup on a single machine?

For example, I don't plan on doing this at present, but:

I have the idea that I can create a snapshot of an LV (in this case, say, on Instance01) and it will contain all changes made to the original since the creation of the snapshot. If a change happens while this LV is mounted on Instance02, are these changes lost? Will rebooting back into Instance01 cause a sudden rush of updates to the snapshot, or are the changes lost Will the snapshot be hopelesly corrupted?

Or have I completely misunderstood what LVM is about?