Search results

I wasn't getting anywhere with ACLs so tried to revist the approach with lxc.idmap, basically following the approach set out in my first post above (and ensuring I corrected the typo for the group) and also following ObsidianBlk's advice and changing ownership to UID 2000 at the host level. I...

I tried something simple to try to narrow down what was causing the problem, so at the host level I ran: chmod -R o+w /vdata After doing so, I entered into a couple of containers and could write in /vdata in both. So the issue seems to be with ACL. I'd very much like to try to preserve what...

Hmmm. This gets curiouser and curiouser. I have another set of 2 drives set up as a ZFS RAID 1 zpool. In the host, it's mounted as /zdata. /zdata is bind mounted in one container in the same manner as /vdata. When I enter into that container, I can write just fine to /zdata, but not /vdata...

Thanks Oguz. Sorry just to clarify I abandoned the approach with uid mapping some time ago and instead use setfacl at the host level to assign rights to users within each container. I have no uid mappings at all for any of the containers. Not sure if this is helpful but I tried manually...

Thanks again Oguz. Yes, the mappings are still there. I did not change them either during or after the upgrade. Just to see if perhaps the defaults had changed, I just now tried adding "acl=1" and "ro=0" to the mountpoint line in one of the containers, each individually and then both...

Thank you for the quick response Oguz. The containers were previously unprivileged. I did not do a backup and restore. I did an in-place upgrade following the steps of the upgrade guide and things appeared to go smoothly during that process. Sorry, I should have also mentioned that I can see...

Sorry to revive an old thread. I recently upgraded to 6.0 and have started to encounter problems with permissions once again. Just to recap, I am using mount points to allow access within containers to certain directors on a physical drive attached to a single node and am using setfacl at the...

Understood. OK thanks Dominik.

Thank you Dominik. I'll try again but this time will remove rpool2 storage first in the GUI. I searched the forums both for the message you cited above (regarding ovs-vswitchd). The only thing I found was this post, which suggests the message is harmless. In my case, it doesn't seem harmless as...

Hmm. This seems to be getting worse. The GUI has become non-responsive when selecting any container. Just shows "loading" with a spinner for each of the containers.

Things have become a bit more interesting. After the export, I tried starting the containers back up but none of them will start. However, this time it seems it's due to a different error - all the subvol directories are mounted and intact. When I run journalctl -xe I see entries like this for...

Here is the output of zfs get all | grep "mounted" after I execute zpool export rpool2: rpool mounted yes - rpool/ROOT mounted yes - rpool/ROOT/pve-1 mounted yes...

It turns out I'm having just a bit of trouble doing this. When I run zpool export rpool2, it goes offline very briefly, but then literally within a few seconds seems to be automatically imported again and shows as online, without me entering any zpool import command. This makes it a bit tricky...

Thank you Dominik. I will check to confirm they are empty. Sorry, just to clarify, currently I use the ZFS pool mounted as /rpool2 to store root directories for containers. It was set up in PVE as ZFS storage. You had indicated that mkdir and is_mountpoint can only be used for directory...

Thanks very, very much Dominik. I will read up on systemd and figure out how to reorder things. Can I perhaps just trouble you for the time being with just one additional question? I'm a bit of a ZFS neophyte and previously ended up completely messing up the prior iteration of my system as a...

Sorry - I should have mentioned that the "rpool2pve" entry in storage.cfg was just created after I read your post about mkdir and is_mountpoint only working for directories. I haven't moved anything just yet - just added the directory and the storage in the GUI. I should also note that the above...

Happy to oblige Dominik. I have a *ton* of other stuff and happy to provide anything else that may be needed. /etc/pve/storage.cfg: dir: local path /var/lib/vz content backup,iso,vztmpl zfspool: local-zfs pool rpool/data content images,rootdir sparse 1...

I'll try to be succinct with this initial post but I have quite a bit more information compiled to date, so if more is needed just let me know. In brief, I set up this new ZFS pool (rpool2) as I was running out of storage on the initial pool (rpool) on which PVE was installed. I moved all my...

Yes, that's right. It's a ZFS pool comprised of two mirrored SSDs that I had set up through the PVE GUI. And thank you, I wasn't aware that these only work for directory storages. Are there equivalent parameters that would work for ZFS pools? Or alternatively would these parameters work if I...

Nevermind - looks like it took after another try. As an aside though, does anyone know why I received those messages on mkdir and is_mountpoint in my storage.cfg? Have those been deprecated?