On Fri, Jul 15, 2016 at 01:34:25AM -0400, Benjamin Kaduk wrote: > On Thu, 14 Jul 2016, Jonathan A. Kollasch wrote: > > > I currently see similar issues with Debian Wheezy and Debian Jessie. > > 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.
Wheezy machine: # uname -a Linux tazenda 3.2.0-4-amd64 #1 SMP Debian 3.2.81-1 x86_64 GNU/Linux # dpkg -l |grep linux-image-|grep -v dummy|grep -v meta ii linux-image-3.2.0-4-amd64 3.2.81-1 amd64 Linux 3.2 for 64-bit PCs # dpkg -l |grep openafs ii openafs-client 1.6.1-3+deb7u6 amd64 AFS distributed filesystem client support ii openafs-krb5 1.6.1-3+deb7u6 amd64 AFS distributed filesystem Kerberos 5 integration ii openafs-modules-dkms 1.6.1-3+deb7u6 all AFS distributed filesystem kernel module DKMS source # find /lib/modules/3.2.0-4-amd64 -name openafs\* -ls 213952 1120 -rw-r--r-- 1 root root 1141072 Jul 10 17:29 /lib/modules/3.2.0-4-amd64/updates/dkms/openafs.ko # uptime 12:06:22 up 4 days, 18:31, 2 users, load average: 0.13, 0.10, 0.12 Jessie machine: # uname -a Linux eternium 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux # dpkg -l |grep linux-image-|grep -v dummy|grep -v meta ii linux-image-3.16.0-4-amd64 3.16.7-ckt25-2 amd64 Linux 3.16 for 64-bit PCs # dpkg -l |grep openafs ii openafs-client 1.6.9-2+deb8u5 amd64 AFS distributed filesystem client support ii openafs-krb5 1.6.9-2+deb8u5 amd64 AFS distributed filesystem Kerberos 5 integration ii openafs-modules-dkms 1.6.9-2+deb8u5 all AFS distributed filesystem kernel module DKMS source # find /lib/modules/3.16.0-4-amd64 -name openafs\* -ls 130407 1352 -rw-r--r-- 1 root root 1383176 May 13 15:33 /lib/modules/3.16.0-4-amd64/updates/dkms/openafs.ko # uptime 12:13:25 up 4 days, 19:20, 2 users, load average: 0.00, 0.04, 0.08 > > git gc consistently fails with ETIMEDOUT for the same path on both > > machines. My fileservers have not changed recently. > > > > When I mentioned this #openafs on Freenode, Benjamin Kaduk seemed to > > think this problem exists in the client/cache manager. > > There are new issues in recent versions of the openafs client that can > manifest like this ... but that would not explain anything if you are > using the versions from wheezy or even jessie. > > -Ben > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
