Category: proxmox

i have containers which mount smb shares from a freebsd server. i added the smb shares to the fstab within the container. the container is privileged and cifs is checked for options in proxmox. i noticed that mounting would not occur properly. sometimes they would mount, sometimes they would not, sometimes one would and the rest wouldn’t. i added _netdev to the fstab options. i only tried once so far but they all mounted this time. _netdev is a flag that makes the mount wait for a network device prior to attempting the mount. i thought that this was done automatically if cifs was being used in fstab. maybe i am wrong or maybe proxmox needs this for containers when they boot? i only tested it once because i cant just keep rebooting this container. i may try another container just to see how it goes. but the first time seemed to work fine. hopefully this is no longer a problem.

so i set up proxmox a while back and its installer doesn’t partition disks for swap space. so i used a zvol to create swap. i noticed that some containers just absolutely lose it for some reason when they begin swapping. it makes no sense and i haven’t quite figured out the reason why. it seems related to older posts about proxmox losing swap control because cgroup2 was not implemented but later it seems that this was supposed to be fixed. swapping is typically abnormal anyways. the solution was to just give the main culprit more ram and disable swap. this seems to be doing the trick but i would like to sort out exactly why this is happening. i don’t want to bump into oom (out of memory) issues in the container (which has been given 16GB of my 64GB in my awesome ryzen proxmox server).