On 9/8/2020 1:31 PM, Sebby, Brian A. ([email protected]) wrote: > Hi, > > I have a few legacy RHEL 6 servers that are still running an older 1.6.x > series DKMS client, which were recently patched and rebooted. On a > couple of them, access to AFS is now just hanging – and I cannot figure > out why. They have the same kernel release and kernel module as some > other systems on the same network that are working, so it doesn’t look > like it would be any sort of firewall issue. Would anyone have any > suggestions on how to debug this? I don’t know if I can upgrade them to > 1.8 since we are trying to keep our legacy systems fairly static.
I debugged one of the problem systems. The issue would not be fixed by any newer version of OpenAFS. The underlying problem is related to the computation of the rx interface MTU when the host has a network interface with an MTU smaller than the minimum jumbo packet size. The work around is "afsd -rxmaxmtu <N>" where N = <network-mtu> - 56 It should be noted that unlike the OpenAFS servers and the Windows client, the UNIX cache manager does not disable jumbo by default. Jeffrey Altman AuriStor, Inc.
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
