To sum up, I have a debian LXC container running samba4. I share a network directory that is a PVE mount point (mp0) on a RAID10 directory with mdadm.
During the transfer of large file in writing to the SAMBA4 server, I have a drop in RAM that tends to 0 from the container, verifiable with the 'top' command.
This is worrisome because when it's zero, I have the transfer that also falls to zero, the pve kernel that logs a samba4 crash.
I tried on another container with the samba4 packages proposed with debian. I have the same problem.
However, on a virtual machine (kvm), with a sata1 mount point, I no longer have the problem, the transfer is done without memory loss.
I tested other mount point, like a ZFS0 with 2 disks, no problem, just like a ZFS0 SSD.
Apart from passing the RAID10 to ZFS, a track to dig?
During the transfer of large file in writing to the SAMBA4 server, I have a drop in RAM that tends to 0 from the container, verifiable with the 'top' command.
This is worrisome because when it's zero, I have the transfer that also falls to zero, the pve kernel that logs a samba4 crash.
I tried on another container with the samba4 packages proposed with debian. I have the same problem.
However, on a virtual machine (kvm), with a sata1 mount point, I no longer have the problem, the transfer is done without memory loss.
I tested other mount point, like a ZFS0 with 2 disks, no problem, just like a ZFS0 SSD.
Apart from passing the RAID10 to ZFS, a track to dig?
