Yet another bindmounts/permissions thread. I just cannot understand UID/GUID remapping, after having read every thread I could find, including the proxmox wiki.
I have an external USB 4tb drive served through a raspberry pi that I'm using as a home NAS, but I'd like to migrate all that to be managed by my proxmox node. My first instinct was to create a debian container and set it up the same way I set up the pi: auto mount the drive, serve with samba, and get permissions straight. All went well and I was able to serve the USB drive through a debian CT, except permissions issues. So I tried to do the UID/GID remapping thing, but no matter what I tried, including the wiki example, failed and I was unable to write to the drive from any device. chown -r xxx:xxx /path/to/drive from proxmox yields "operation not permitted." Barring the external USB drive, I now am trying to move my NAS storage to internal sata drives with the same server setup, and I'm running into the same problem. I got the drives mounted, samba'd, and browseable over the home network. Just no write permissions. With Turnkey Fileserver I run into the same problems.
So my questions are these:
I know now that proxmox has resource pool support. Is this a GUI replacement for UID/GID remapping, will it accomplish the same thing?
That said, as far as I understand pools, I need to create a pool and assign the target ZFS drive and samba server to that pool. Then assign a group permission to... datauser? pooluser? I'm getting hung up on this one, not sure which role to choose. If the pool contains the drive as well as the server and has the proper permission, it should accomplish what I need, correct?
Do I still need to remap UID/GID in the host, and would doing that allow root to chown the drive to the remapped UID/GID successfully?
pulling my hair out here trying to figure out where I'm going wrong.
I have an external USB 4tb drive served through a raspberry pi that I'm using as a home NAS, but I'd like to migrate all that to be managed by my proxmox node. My first instinct was to create a debian container and set it up the same way I set up the pi: auto mount the drive, serve with samba, and get permissions straight. All went well and I was able to serve the USB drive through a debian CT, except permissions issues. So I tried to do the UID/GID remapping thing, but no matter what I tried, including the wiki example, failed and I was unable to write to the drive from any device. chown -r xxx:xxx /path/to/drive from proxmox yields "operation not permitted." Barring the external USB drive, I now am trying to move my NAS storage to internal sata drives with the same server setup, and I'm running into the same problem. I got the drives mounted, samba'd, and browseable over the home network. Just no write permissions. With Turnkey Fileserver I run into the same problems.
So my questions are these:
I know now that proxmox has resource pool support. Is this a GUI replacement for UID/GID remapping, will it accomplish the same thing?
That said, as far as I understand pools, I need to create a pool and assign the target ZFS drive and samba server to that pool. Then assign a group permission to... datauser? pooluser? I'm getting hung up on this one, not sure which role to choose. If the pool contains the drive as well as the server and has the proper permission, it should accomplish what I need, correct?
Do I still need to remap UID/GID in the host, and would doing that allow root to chown the drive to the remapped UID/GID successfully?
pulling my hair out here trying to figure out where I'm going wrong.