Hi all,
Thanks to your help, I reverted to a previous version of the Debian
kernel and was able to successfully git clone the troublesome repository.
A working version of the Jessie kernel is:
Linux mcd-db 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5
(2015-10-09) x86_64 GNU/Linux
> I am dismissive of the notion that the server's kernel version
> matters since all of the fileserver code is in userland.
I was vaguely hypothesizing that some networking code changed and goofed
networking up in some way that AFS depends on, but not much else. (Not
much of a hope?)
> Can you please provide actual exact (debian) versions, for both the
> openafs-client and kernel? Attempting to say anything without them
> would require some level of speculation.
See table below....
----------- NOT WORKING ---
1.6.1-3+deb7u6 wheezy 3.2.81-1
1.6.9-2+deb8u4 jessie 3.16.7-ckt25-2
1.6.9-2+deb8u5 jessie 3.16.7-ckt25-2
1.6.14-1 jessie 3.16.7-ckt25-2
1.6.15-1 jessie 3.16.7-ckt25-2
----------- WORKING ---
1.6.9-2+deb8u5 Jessie 3.16.7-ckt11-1+deb8u5
1.6.16 no debian package
1.6.17-2 jessie 3.16.7-ckt25-2
So what next?
Should I be narrowing down which Debian kernel update broke AFS and
report it against their kernel package?
> I believe the Debian and Scientific Linux issues are unrelated because
> the symptoms are so different.
You're most likely right! I tried Scientific Linux again today and
1.6.9 and 1.6.15 from .src.rpm were fine. :/
Thanks again for your help!
Chad.
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
