Hello,
I have what I think may be a stumper!
I need to bind mount some storage into a Container in a way that it is still available when the Container is migrated to a different Proxmox node. I'm pretty sure you can do this with NFS but I cannot do that because the container is serving Samba shares and there is a long standing locking issue between Samba 3 and NFS (unless you tell Samba to do a crappy job of file locking).
So, I need to bind mount shared storage into a Container that isn't coming from NFS, so that the storage is still available post-migration but I can still use Samba. I don't think I can use iSCSI without nuking the filesystem.
Note for future readers: I'm only 99% sure that the parts I just said are already possible really are possible. For example I labbed out a Container serving Samba from an NFS storage item added to Proxmox and bind-mounted into the Container, but I didn't actually migrate it to see if it still worked (aside from the previously mentioned locking issues). So please let me know if I'm actually further from a solution than I think.
The reason for doing the bind mounting here is that the data being served over Samba is over 1TB and I don't want vzdump churning around on that forever every night. I'm also hesitant to store the data inside the Container within a directory that vzdump already skips, and I'm not excited about adding my own exceptions to the backup list. (you probably assumed as much, but yes, the shared data for Samba is already backed up by other means)
Would anyone have any suggestions? Feel free to ask for clarification if some part is unclear.
Thank you,
Mark
I have what I think may be a stumper!
I need to bind mount some storage into a Container in a way that it is still available when the Container is migrated to a different Proxmox node. I'm pretty sure you can do this with NFS but I cannot do that because the container is serving Samba shares and there is a long standing locking issue between Samba 3 and NFS (unless you tell Samba to do a crappy job of file locking).
So, I need to bind mount shared storage into a Container that isn't coming from NFS, so that the storage is still available post-migration but I can still use Samba. I don't think I can use iSCSI without nuking the filesystem.
Note for future readers: I'm only 99% sure that the parts I just said are already possible really are possible. For example I labbed out a Container serving Samba from an NFS storage item added to Proxmox and bind-mounted into the Container, but I didn't actually migrate it to see if it still worked (aside from the previously mentioned locking issues). So please let me know if I'm actually further from a solution than I think.
The reason for doing the bind mounting here is that the data being served over Samba is over 1TB and I don't want vzdump churning around on that forever every night. I'm also hesitant to store the data inside the Container within a directory that vzdump already skips, and I'm not excited about adding my own exceptions to the backup list. (you probably assumed as much, but yes, the shared data for Samba is already backed up by other means)
Would anyone have any suggestions? Feel free to ask for clarification if some part is unclear.
Thank you,
Mark
Last edited: