OK, here is the solution, it's a more complicated than assumed, I don't know if this is the right way - but it works!
First I added a filesystem to my blank SSD, that's the easy part, via SSH:
Code:
mkfs.btrfs /dev/nvme1n1p1
mkdir /mnt/data2
adding this to etc/fstab
Code:
/dev/nvme1n1p1 /mnt/data2 btrfs defaults 0 1
reloading fstab and mount
Code:
systemctl daemon-reload
mount /mnt/data2/
Checking the proxmox node in the Web UI now shows a filesystem and I am probably able to bind-mount it to my containers.
Now to the disk that my proxmox is running on. The installation already created a volume group (pve) and some logical volumes). I checked that using those commands:
(lsblk could lead to the same information, but the above commands are more specific).
What we see here is, that there's a couple of space left over. The WebUI does not offer a way to use that, at least I could not find out where. So I first created an additional logical volume for that volume group "pve":
Code:
lvcreate -n data1 --size 1000G pve
and again I created the file system and all that stuff from above...
et voila - at least I have the left-over space now available in /mnt/data1 and mnt/data2.
Now let's get to the sharing-thing.
Now create a fresh container, but deactivate the "unprivileged" feature.
After that I edited the config file for this container, again via shell:
Code:
nano /etc/pve/lxc/101.conf
added those lines:
Code:
mp0: /mnt/data1,mp=/mnt/data1
mp1: /mnt/data2,mp=/mnt/data1
And the ressources area already has been refreshed, nice:
And ls -la /mnt also gives me the folders.
Now lets double check if my use case is working, too: Creating a second container, same settings as above.
What does ls -la /mnt show? The content of my "shared disks"! Beautiful!
Let's do a quick check for this "unprivileged thing": Adding a container that is "unprivileged": Creating, Modifying, Running - and the folders are visible, but not writable!
Perfect! Took my like 6 hours to find that out. Lessons learned: The WebUI is a nice thing, but it is totally not helpful when managing your storage (not complaining, still love proxmox!). So its kind of mandatory to prepare the storage situation via SSH (or the built-in shell of the WebUI) and than spin up your containers.
Thanks for listening - over and out