weird fileserver issues after upgrading to proxmox 9

P

pjottrr

New Member
Nov 4, 2025
9
1
3
So i recently upgaded to proxmox 9, and everything seemed fine.
however, my fileserver ( proxmox helper script for turnkey os with debian bookworm ) had some weird issues

i haven't heard any issues from my jellyfin users ( lxc comtainer, (ubuntu Jammy)), but for myself i ran into issues playing files in windows straight from the file server. To sum up what happens, it comes down to ; if i want to copy a file it will copy for 15 seconds with 100MB/s , then wait for 10 seconds, end then starts copying again. , when doing the same from other windows pc's , vlc playback or whatever, the timestamps are always the same . So at time x the entire file server stops for 10 seconds....
I still haven't figured out what it was , but since it cost me a few hours, I'd thought, lets post this so maybe someone else can benefit from what I've learnt.

so in the end i decided to take a new Debian lxc container ( trixie) and rebuild the file server with that, since turnkey has way more features then i need.....
since the storage can be directly attached from the proxmox server , the entire test of using another machine only took 15 minutes or so...

and all was working like never before, constant transfers of files of around 220 MB/s and no stops at all

So something is wrong with my turnkey server, but i can't figure out what.
I did test copying files ( scp) from on lxc container to the other in Linux lxc's ad that didn't seem to produce any issues or hick-ups.
also a transfer ( scp) from the turnkey server into the local storage of my backup proxmox server had no issues.
only issues was from the turnkey server into windows. and i still have no clue why.
i saved the server, and it is turned off, maybe with the right suggestions i can try to figure out what's wrong with it , so others can benefit.
so all i have left is the system specs i guess:


server:
4 x AMD Ryzen 3 3200G with Radeon Vega Graphics (1 Socket)
Kernel Version

Linux 6.14.11-3-pve (2025-09-22T10:13Z)


EFI


pve-manager/9.0.11/3bf5476b8a4699e2


ram: 16 gb
networking: 2.5 gb nic
storage:
ntfs filesystem ( yes i know it's uncommon... but the storage was yanked from my windows desktop, it's been running for years)
Adaptec ASR8805 raid controller with 3 8-tb disks in raid 5 mode

windows desktop:
not really relevant i guess, decent gaming rig with 2.5 gb nic
 
so apparently these forums are so popular that this topic has went down faster then i would imagine.

anyone here who thinks it is still interesting to investigate / help find out why this issue happened ? I'll keep this topic open for some time, but if there are , again no responses, i'll remove the old fileserver
 
could you post your lxc container configuration, your samba configuration from inside container and your storage.cfg from /etc/pve and the output of the "mount" command ?
 
of cource i will :)

first of all, since the storage.cfg doesn't show the disk, because it is a physical disk in proxmox, hereby the image:

1762721979561.png


storage.cfg from pve:

dir: local
path /var/lib/vz
content iso,vztmpl,backup

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

pbs: Backup1
datastore store1
server 192.168.1.148
content backup
fingerprint "fingerprint removed"
prune-backups keep-all=+1
username root@pam




then the broken fileserver:


config of the broken turnkey fileserver:
_____________________________________________________________
/etc/pve/lxc# cat 102.conf

arch: amd64
cores: 4
features: keyctl=1,nesting=1
hostname: fileserver
memory: 2048
mp0: /mnt/E,mp=/E
net0: name=eth0,bridge=vmbr0,gw=192.168.1.250,hwaddr=BC:24:11:8D:D9:D4,ip=192.168.1.181/24,type=veth
net1: name=dockerbackup,bridge=vmbr201,gw=192.168.201.250,hwaddr=BC:24:11:67:C0:DC,ip=192.168.201.5/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-102-disk-0,size=8G
startup: order=2
swap: 512
tags: proxmox-helper-scripts
unprivileged: 1
root@Jupiter:/etc/pve/lxc#


smb.conf

[global]
workgroup = WORKGROUP
netbios name = FILESERVER
server string = FileServer

os level = 20
security = user
passdb backend = tdbsam

#uncommenting the following parameter will prevent any guest access (public sharing)
#restrict anonymous = 2
#used for guest access
map to guest = bad user

admin users = root
encrypt passwords = true
obey pam restrictions = yes
pam password change = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

add user script = /usr/sbin/useradd -m '%u' -g users -G users
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'

guest account = nobody

log file = /var/log/samba/samba.log
max log size = 1000

wins support = yes
dns proxy = no

socket options = TCP_NODELAY
panic action = /usr/share/samba/panic-action %d

vfs object = recycle
recycle:touch = yes
recycle:keeptree = yes
recycle:versions = yes
recycle:exclude_dir = tmp quarantine

[homes]
comment = Home Directory
browseable = no
read only = no
valid users = %S

[cdrom]
comment = CD-ROM
read only = yes
locking = no
guest ok = yes
path = /media/cdrom
preexec = /bin/mount /media/cdrom
postexec = /bin/umount /media/cdrom

[storage]
comment = E-schijf
path = /E
browseable = yes
read only = no
create mask = 0755
directory mask = 0755
guest ok = no



_________________________________________________________________________



as seen in the image , /dev/sda2 is a phisical disc, in this case a raid storage device ( Adaptec ASR8805), and /E is an ntfs filesystem from a previous windows host

mount command from inside the turnkey broken server:

/dev/mapper/pve-vm--102--disk--0 on / type ext4 (rw,relatime,stripe=16)
/dev/sda2 on /E type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
none on /dev type tmpfs (rw,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys type proc (ro,relatime)
proc on /proc/sysrq-trigger type proc (ro,relatime)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
sysfs on /sys/devices/virtual/net type sysfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
proc on /dev/.lxc/proc type proc (rw,relatime)
sys on /dev/.lxc/sys type sysfs (rw,relatime)
none on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
lxcfs on /proc/cpuinfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/diskstats type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/loadavg type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/meminfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/slabinfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/stat type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/swaps type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/uptime type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /sys/devices/system/cpu type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
udev on /dev/full type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/null type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/random type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/tty type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/urandom type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/zero type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/ptmx type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/console type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/tty1 type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/tty2 type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
none on /proc/sys/kernel/random/boot_id type tmpfs (ro,nosuid,nodev,noexec,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,uid=100000,gid=100000,inode64)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=2847272k,nr_inodes=819200,mode=755,uid=100000,gid=100000,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,uid=100000,gid=100000,inode64)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)







and lastly , the good functioning server:

this is a default debian lxc container:
lxc config:
root@Jupiter:/etc/pve/lxc# cat 114.conf
#<div align='center'>
# <a href='https://helper-scripts.com' target='_blank' rel='noopener noreferrer'>
# <img src='https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/images/logo-81x112.png' alt='Logo' style='width%3A81px;height%3A112px;'/>
# </a>
#
# <h2 style='font-size%3A 24px; margin%3A 20px 0;'>Debian LXC</h2>
#
# <p style='margin%3A 16px 0;'>
# <a href='https://ko-fi.com/community_scripts' target='_blank' rel='noopener noreferrer'>
# <img src='https://img.shields.io/badge/&#x2615;-Buy us a coffee-blue' alt='spend Coffee' />
# </a>
# </p>
#
# <span style='margin%3A 0 10px;'>
# <i class="fa fa-github fa-fw" style="color%3A #f5f5f5;"></i>
# <a href='https://github.com/community-scripts/ProxmoxVE' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>GitHub</a>
# </span>
# <span style='margin%3A 0 10px;'>
# <i class="fa fa-comments fa-fw" style="color%3A #f5f5f5;"></i>
# <a href='https://github.com/community-scripts/ProxmoxVE/discussions' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Discussions</a>
# </span>
# <span style='margin%3A 0 10px;'>
# <i class="fa fa-exclamation-circle fa-fw" style="color%3A #f5f5f5;"></i>
# <a href='https://github.com/community-scripts/ProxmoxVE/issues' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Issues</a>
# </span>
#</div>
arch: amd64
cores: 1
features: keyctl=1,nesting=1
hostname: debian
memory: 512
mp0: /mnt/E/,mp=/E
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:CF:0C:13,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-114-disk-0,size=2G
swap: 512
tags: community-script;os
unprivileged: 1
root@Jupiter:/etc/pve/lxc#

output of the "mount command" :


root@debian:/home# mount
/dev/mapper/pve-vm--114--disk--0 on / type ext4 (rw,relatime,stripe=16)
/dev/sda2 on /E type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
none on /dev type tmpfs (rw,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys type proc (ro,relatime)
proc on /proc/sysrq-trigger type proc (ro,relatime)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
sysfs on /sys/devices/virtual/net type sysfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
proc on /dev/.lxc/proc type proc (rw,relatime)
sys on /dev/.lxc/sys type sysfs (rw,relatime)
none on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
lxcfs on /proc/cpuinfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/diskstats type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/loadavg type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/meminfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/slabinfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/stat type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/swaps type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/uptime type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /sys/devices/system/cpu type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
udev on /dev/full type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/null type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/random type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/tty type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/urandom type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
udev on /dev/zero type devtmpfs (rw,nosuid,relatime,size=7079736k,nr_inodes=1769934,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/ptmx type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/console type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/tty1 type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
devpts on /dev/tty2 type devpts (rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026)
none on /proc/sys/kernel/random/boot_id type tmpfs (ro,nosuid,nodev,noexec,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,uid=100000,gid=100000,inode64)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=2847272k,nr_inodes=819200,mode=755,uid=100000,gid=100000,inode64)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=7118176k,nr_inodes=1048576,uid=100000,gid=100000,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,uid=100000,gid=100000,inode64)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-journald.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700)
ramfs on /run/credentials/systemd-networkd.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700)
ramfs on /run/credentials/container-getty@2.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700)
ramfs on /run/credentials/container-getty@1.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700)
ramfs on /run/credentials/console-getty.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700)
tmpfs on /run/user/1002 type tmpfs (rw,nosuid,nodev,relatime,size=1423632k,nr_inodes=355908,mode=700,uid=101002,gid=101002,inode64)
root@debian:/home#


smb.conf ( since it has been an scp from the old one, it is exactly the same) :
root@debian:/etc/samba# cat smb.conf
[global]
workgroup = WORKGROUP
netbios name = FILESERVER
server string = FileServer

os level = 20
security = user
passdb backend = tdbsam

#uncommenting the following parameter will prevent any guest access (public sharing)
#restrict anonymous = 2
#used for guest access
map to guest = bad user

admin users = root
encrypt passwords = true
obey pam restrictions = yes
pam password change = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

add user script = /usr/sbin/useradd -m '%u' -g users -G users
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'

guest account = nobody

log file = /var/log/samba/samba.log
max log size = 1000

wins support = yes
dns proxy = no

socket options = TCP_NODELAY
panic action = /usr/share/samba/panic-action %d

vfs object = recycle
recycle:touch = yes
recycle:keeptree = yes
recycle:versions = yes
recycle:exclude_dir = tmp quarantine

[homes]
comment = Home Directory
browseable = no
read only = no
valid users = %S

[cdrom]
comment = CD-ROM
read only = yes
locking = no
guest ok = yes
path = /media/cdrom
preexec = /bin/mount /media/cdrom
postexec = /bin/umount /media/cdrom

[storage]
comment = E-schijf
path = /E
browseable = yes
read only = no
create mask = 0755
directory mask = 0755
guest ok = no




I think that's about it. , if you need more info , please let me know
 
Last edited:
you mean you have a second lxc container which works without problems?

those are both turnkey linux lxc containers, or what?

the one with the issue has docker inside?
 
  • Like
Reactions: Johannes S
yes, he turnkey fileserver ( lxc) , or the faulty server, is the one i wrote first about

my solution was to build a new file server , and since turnkey had way more stuff in it then i needed ( i only need samba) i decided to go with a Debian lxc container.

to my surprise it worked flawlessly , and performance on this Debian lxc works perfectly , i can copy files with the speed of my network in stead of the wonky state this turnkey file server is in.

point is still,
what i did was upgrade to proxmox 9 , and after the upgrade, proxmox started behaving like his.
and you can say "so what's the problem then , you fixed it... ? "

well , i'd like to know what's wrong and understand why this turnkey fileserver is so wonky, and a new server is not
 
i would first disable net1 temporarly in the old and then provide 4 cores and 2048mb to the new lxc

comparing two different operating systems is hard enough - but they should have the same lxc/hardware ressources

i guess the most prominent different between the two lxc here should be samba versions. please provide/compare those

the behaviour of restarting copy reminds me to some samba bug/issue when storage is slower then networking, so check memory usage of smbd processes during copy and if smbd crashes and get new pid during copy
 
Last edited:
  • Like
Reactions: Johannes S
so i disabled ( removed) net 1 from broken server

and the problem is gone, :)
no more hiccups ... performance is a bit on the low side, but no full hiccups here ,

so i reinstated net 1 , and the problem returned

this is how it looks when copying when the problem exists:

1762760013404.png



when i copy files and it hangs, and you see the speed in the above windows graph going down to 13 megs, but that is actually nothing .... it is the graph trying to average itself out.
the pid of the samba process stays the same ... so it doesn't restart



Anyway, thnx for helping figure this problem out
at least now we know what caused it.
i stil don't know why that 2nd network line causes is , and i don't think it is too interesting to know ?


if you guys think it is interesting to figure out ... i'll check back at the end of the day

btw , as one of the questions was about the samba server;

the samba version is: Samba version 4.17.12-Debian on the old server and Samba version 4.22.4-Debian-4.22.4+dfsg-1~deb13u1 on the new server
 
  • Like
Reactions: RolandK
@RolandK yeah, same here... no clue if it is interesting to figure it out

Maybe this topic might be usefull for someone else running into those strange errors.


@Onslow , in all cases the mtu is the same ( same as bridge)

i don't know why having that 2nd network is causing the issue , but somehow it does.
to me , this sounds like a problem with turnkey, but i could also try creating this 2nd network on the new server, see if the problem allo starts happening on the new fileserver
 
ok, so i added this line to my new fileserver:
net1: name=dockerbackup,bridge=vmbr201,hwaddr=BC:24:11:67:C0:DC,ip=192.168.201.5/24,type=veth

and the problem immediately appeared on the new server, and just for clarification,
i don't use that network on the fileserver, it is / was there by mistake.

it seems like something in the network-stack is not behaving properly / as expected
Maybe this problem is a bit bigger then i thought , and i don't think it's a good idea to leave it at this
so i rambled some stuff and AI made a coherent story of it, but it contains some double / previously explained stuff .... but i thought it might be better so everyone can read it instead of reading back the entire conversation. :

{/start AI coherent response}
My Setup

  • Physical Network: My 1Gbps internet connects to a managed switch. A 2.5Gbps link goes from that switch to a 2.5Gbps NIC on the PVE server.
  • Firewall/Router: An OPNsense VM, running on the same PVE host, manages all my VLANs and virtual networks.
  • Problematic Network (vmbr201): I have a bridge named vmbr201. Two isolated WordPress sites, running in Docker containers, and a fileserver are connected to this network for isolation.
    • (Note: I had previously named the interface 'dockerbackup', which was a poor choice since it's actually for these WordPress sites.)
  • Working Network (vmbr0): I have a bridge named vmbr0. The fileserver and a windows desktop are connected to this network.

The Problem​

I set up a new fileserver and it works perfectly on vmbr0 and a Windows desktop.
I then added it to the vmbr201 network using this line:
net1: name=dockerbackup,bridge=vmbr201,hwaddr=BC:24:11:67:C0:DC,ip=192.168.201.5/24,type=veth

The immediate issue: As soon as I started a file copy (using Samba) on this new fileserver, the load on both WordPress Docker sites—which are on the same vmbr201 bridge—became extremely high.

  • This was not a CPU usage issue on the WordPress sites.
  • The WordPress sites are not heavily used, so this load was clearly abnormal.


Troubleshooting / Findings​


My key finding is:
When I removed the vmbr201 network interface from the fileserver, the load on the WordPress sites immediately returned to normal.
This strongly suggests the fileserver's Samba traffic is somehow interfering with or overwhelming other services on the same network bridge, even though they aren't directly interacting. It feels like something in the network stack is not behaving as expected, and I'm not sure where to look next.

Here is the image showing the network interfaces:

{/end AI response}


so here is my opnsense network config:
i hope you guys have some ideas.

1762783676433.png
 
so to conclude , it is a dhcp vs static issue:

not working / having issues :
net1: name=dockerbackup,bridge=vmbr201,hwaddr=BC:24:11:67:C0:DC,ip=192.168.201.5/24,type=veth

working:

net1: name=net2,bridge=vmbr201,firewall=1,hwaddr=BC:24:11:C2:27:DA,ip=dhcp,type=veth


so i looked at the DHCP settings, it looked like this
net2@if49: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:24:11:c2:27:da brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.201.3/24 brd 192.168.201.255 scope global dynamic net2
valid_lft 6396sec preferred_lft 6396sec
inet6 fe80::be24:11ff:fec2:27da/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever


i then set it to static again:

1762943223106.png
and:
net2@if49: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:24:11:c2:27:da brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.201.3/24 brd 192.168.201.255 scope global dynamic net2
valid_lft 4545sec preferred_lft 4545sec
inet6 fe80::be24:11ff:fec2:27da/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever



and guess what , performance is terrible again.

not sure why , but it is very much measurable. as soon as i remove the static connection and change net1 to dhcp , the issues are gone, and switching back to static intantly the problems return

and again, just to clarify, i don't use net1 , it's a totally different network to what i used
net0 is the one i use for file-transfers ....
 
Last edited:
You must log in or register to reply here.
Top Bottom