On Sat, 16 Jul 2016, Benjamin Kaduk wrote:
> On Fri, 15 Jul 2016, Jonathan A. Kollasch wrote:
>
> > 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
Hi Mark,
> Ahh. But what about 1.6.16?
Sorry, in my table under "working" I had listed confusingly listed
1.6.16 with "no debian package". This was a remnant from when I was
testing Scientific Linux and was tracking the two distro's versions
together.
I haven't tested 1.6.16 in Debian.
On Fri, 15 Jul 2016, Jonathan A. Kollasch wrote:
> 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
On Jul 16, 2016, at 12:43 AM, Benjamin Kaduk
wrote:
> On Sat, 16 Jul 2016, Mark Vitale wrote:
>
>>
>> On Jul 15, 2016, at 10:39 PM, Chad William Seys
>> wrote:
>>> I found the break point in when openafs starts having problems with git
>>> checkout
On Sat, 16 Jul 2016, Mark Vitale wrote:
>
> On Jul 15, 2016, at 10:39 PM, Chad William Seys
> wrote:
> > I found the break point in when openafs starts having problems with git
> > checkout on my test repo:
> >
> > First broken: 3.16.7-ckt25-1(compiled
On Jul 15, 2016, at 10:39 PM, Chad William Seys wrote:
> I found the break point in when openafs starts having problems with git
> checkout on my test repo:
>
> First broken: 3.16.7-ckt25-1(compiled 2016-03-06)
> Last working: 3.16.7-ckt20-1+deb8u4
>
> Here
Hi all,
I found the break point in when openafs starts having problems with
git checkout on my test repo:
First broken: 3.16.7-ckt25-1(compiled 2016-03-06)
Last working: 3.16.7-ckt20-1+deb8u4
Here is a changelog in case someone knows what to hunt for in:
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
>
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?
On 2016-07-15 07:34, 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
On Thu, 14 Jul 2016, Chad William Seys wrote:
> Hi Ben,
>
> The Scientific Linux clients are using patched (by Redhat) 2.6.32 and the
> Debian clients are using patched (by Debian) 3.2.78 and 3.16.7 .
>
> Do you suspect that a recent security patch, applied to all three kernels,
> could have
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.
On 7/14/2016 6:18 PM, Chad William Seys wrote:
> Hi Ben,
>
> The Scientific Linux clients are using patched (by Redhat) 2.6.32 and
> the Debian clients are using patched (by Debian) 3.2.78 and 3.16.7 .
>
> Do you suspect that a recent security patch, applied to all three
> kernels, could have
Hi Ben,
The Scientific Linux clients are using patched (by Redhat) 2.6.32 and
the Debian clients are using patched (by Debian) 3.2.78 and 3.16.7 .
Do you suspect that a recent security patch, applied to all three
kernels, could have broken the older AFS clients?
I could certainly test this
On Thu, 14 Jul 2016, Chad William Seys wrote:
> Hi Jonathan,
>
> Well it is good to hear that someone else is having a similar problem!
>
> > When I mentioned this #openafs on Freenode, Benjamin Kaduk seemed to
> > think this problem exists in the client/cache manager.
>
> So a bug in
Hi Jonathan,
Well it is good to hear that someone else is having a similar problem!
When I mentioned this #openafs on Freenode, Benjamin Kaduk seemed to
think this problem exists in the client/cache manager.
So a bug in client/cache manager?
Why would it be triggered now?
It seems as though
On Thu, Jul 14, 2016 at 02:55:49PM -0500, Chad William Seys wrote:
> Hi all,
> We have begun suddenly begun experiencing client failures and are
> trying
> to determine what is going on.
>
> openafs-client versions 1.6.9, 1.6.14, 1.6.15 fail in various ways*. On
> Debian we can
Hi all,
We have begun suddenly begun experiencing client failures and are
trying
to determine what is going on.
openafs-client versions 1.6.9, 1.6.14, 1.6.15 fail in various ways*. On
Debian we can reproduce the problem by 'git checkout' a particular repo. It
fails with a "Connection
18 matches
Mail list logo