> I don't understand how multiple TCP connections to the same
> server IP address will distribute the load across multiple network
> interfaces?
> I thought that lagg would have handled this?
A lagg typically keeps all data in a TCP stream on a specific lagg member
(depending on how the lagg i
Hmmm..
We might have run into the same situation here between some Linux (CentOS
7.9.2009) clients and our FreeBSD 12.2 nfs servers this evening when a network
switch in between the nfs server and the clients had to be rebooted causing a
network partitioning for a number of minutes.
Not every
CLOSE_WAIT on the server side usually indicates that the kernel has sent the
ACK to the clients FIN (start of a shutdown) packet but hasn’t sent it’s own
FIN packet - something that usually happens when the server has read all data
queued up from the client and taken what actions it need to shut
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253708
Whenever I try to boot a Dell R730xd server with FreeBSD 12.2-RELEASE-p3 it
always locks up on boot - when attempting to enable the second Intel ixl 10G
ethernet interface in a lagg (failover) link. Unless I enable verbose boot -
then it
I once reported that we had a server with many thousands (typically 23000 or so
per server) ZFS filesystems (and 300+ snapshots per filesystem) where mountd
was 100% busy reading and updating the kernel (and while doing that holding the
NFS lock for a very long time) every hour (when we took sna
