Hi
I added a turnkey-fileserver LXC to my Proxmox 9.1 node so I can access a 4TB SSD over SAMBA.
I configured it so I can access my share from Windows 11 which is fine. However, I noticed that write speeds to the share are VERY slow.
Across my 2.5gbe NIC, I can read from the share at approx 280MB/s but when writing to the same share the transfer almost grinds to a complete stop and averages out at around 3MB/s !! In most cases i have to cancel the transfer because it is so slow!
I basically used - mp0: /mnt/Backup,mp=/mnt/Backup inside my LXC config. I can browse the share /mnt/Backup in proxmox console and LXC console.
I thought the issue might be my SATA SSD and/or controller connected to my proxmox node so I ran a speed test directly on the disk and the write speed was on avg 370MB/s so defo not a controller/disk issue.
I then created a new share on the QEMU disk and did the same test, absolutely no issues. So the problem is related to shares presented via a bind mount.
Does anyone know what the issue might be? I changed to priveleged for the container but that made no difference. Tearing my hair out with this one!
I added a turnkey-fileserver LXC to my Proxmox 9.1 node so I can access a 4TB SSD over SAMBA.
I configured it so I can access my share from Windows 11 which is fine. However, I noticed that write speeds to the share are VERY slow.
Across my 2.5gbe NIC, I can read from the share at approx 280MB/s but when writing to the same share the transfer almost grinds to a complete stop and averages out at around 3MB/s !! In most cases i have to cancel the transfer because it is so slow!
I basically used - mp0: /mnt/Backup,mp=/mnt/Backup inside my LXC config. I can browse the share /mnt/Backup in proxmox console and LXC console.
I thought the issue might be my SATA SSD and/or controller connected to my proxmox node so I ran a speed test directly on the disk and the write speed was on avg 370MB/s so defo not a controller/disk issue.
I then created a new share on the QEMU disk and did the same test, absolutely no issues. So the problem is related to shares presented via a bind mount.
Does anyone know what the issue might be? I changed to priveleged for the container but that made no difference. Tearing my hair out with this one!
Last edited: