I want to use some part of free space that is inside Qubes OS default encrypted LVM.
E.g. I want to create several partitions and mount them to the Windows (as a second D disk) and fedora-template qubes.
This way I will be able easily backup files from these disks, even from other qubes.
I would be happy for advice and answers:
Is it OK to use Qubes OS LVM pool for creating own partitions that Qubes OS knows nothing about? Can it break things, like internal counters or any other contracts that the system expects? Maybe some additional information about naming this partitions, making them or anything?
How should I attach such a partition? Is it possible to attach it as usual block device?
Does somebody uses setup like that? Maybe for sharing/moving a large amount of data between 2 or more qubes? What is the best way and setup to such things?
E.g. I want to create several partitions and mount them to the Windows (as a second D disk) and fedora-template qubes.
This way I will be able easily backup files from these disks, even from other qubes.
I would be happy for advice and answers:
Yes
Not in my experience.
It’s just a standard pool: treat it as such
Attach it with qui-devices as any other device.
Yes.
For sharing/moving a large amount of data on a more regular basis, I use rsync over
qrexec, or syncthing - both
packaged as part of the tasks project
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
Because it is encrypted on the higher level, than filesystem. All pool is encrypted, and encryption does not care if partitions have ext4, ntfs or any raw binary data.
Thanks, @unman, for your sufficient answer, I am marking it as a Solution.
About attaching with qvm-devices I have a question though. Aren’t all LVM partitions hidden in Qubes OS (via udev) from showing in the qvm-devices?
I thought that I will have to do something with qubesdb- tools or something to make it work.