Re: [OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-28 Thread Brandon Allbery
On Thu, 2014-02-27 at 23:30 -0600, Andrew Deason wrote: > As for what is triggering this behavior, as far as I can tell it's > just > a normal short read from the fssync socket. That is, one side sends > 292 > bytes, and the other receives 200 bytes (and then would receive > another > 92 bytes if i

[OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-27 Thread Andrew Deason
On Mon, 17 Feb 2014 14:13:00 -0600 Andrew Deason wrote: > On Thu, 13 Feb 2014 00:13:41 -0600 > Tracy Di Marco White wrote: > > > VolserLog (yesteday) > > Wed Feb 12 01:04:48 2014 SYNC_ask: length field in response inconsistent > > on circuit 'FSSYNC' command 65543, 200 != 292 > > Thanks for t

[OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-17 Thread Andrew Deason
On Thu, 13 Feb 2014 00:13:41 -0600 Tracy Di Marco White wrote: > > < > http://git.openafs.org/?p=openafs.git;a=patch;h=9604a45e94ed23a2941d0a7e11bfd892a0bd0bf7 > > > > VolserLog (yesteday) > Wed Feb 12 01:04:48 2014 SYNC_ask: length field in response inconsistent > on circuit 'FSSYNC' command 6

Re: [OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-12 Thread Tracy Di Marco White
On Mon, Feb 10, 2014 at 2:23 PM, Andrew Deason wrote: > > On Mon, 10 Feb 2014 00:27:59 -0600 > Tracy Di Marco White wrote: > > > VolserLog > > Sat Feb 8 00:02:42 2014 SYNC_ask: length field in response inconsistent > > on circuit 'FSSYNC' > > Sat Feb 8 00:02:42 2014 SYNC_ask: protocol communic

Re: [OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-10 Thread Tracy Di Marco White
On Mon, Feb 10, 2014 at 3:22 PM, Andrew Deason wrote: > On Mon, 10 Feb 2014 15:09:25 -0600 > Tracy Di Marco White wrote: > > I may have misinterpreted something up there. Were you running a prior > 1.6 release with DAFS before, and this just started happening with > 1.6.5? Or did you "switch" t

[OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-10 Thread Andrew Deason
On Mon, 10 Feb 2014 15:09:25 -0600 Tracy Di Marco White wrote: > That's possible, certainly, depending on your definition of 'real'. I > know other people are using DAFS on NetBSD for fileservers. > Personally, I've only been doing it for a year or two. Okay okay; I just meant this isn't exactly

Re: [OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-10 Thread Tracy Di Marco White
On Mon, Feb 10, 2014 at 2:23 PM, Andrew Deason wrote: > On Mon, 10 Feb 2014 00:27:59 -0600 > Tracy Di Marco White wrote: > > > Every night at midnight, we run 'vos backupsys'. For three nights in a > > row, on one of the servers I've upgraded to 1.6.5 and dafs, I've been > > getting the following

[OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-10 Thread Andrew Deason
On Mon, 10 Feb 2014 13:00:48 + p...@afs.list.sabi.co.uk (Peter Grandi) wrote: > That " _VLockFd: conflicting lock held" and "VAttachVolume: > another program has vol locked" looks vaguely familiar, and > in a case that I have seen it was because a DB server was > offline, and 'vos' took a

[OpenAFS] Re: nightly failure since upgrading to 1.6.5

2014-02-10 Thread Andrew Deason
On Mon, 10 Feb 2014 00:27:59 -0600 Tracy Di Marco White wrote: > Every night at midnight, we run 'vos backupsys'. For three nights in a > row, on one of the servers I've upgraded to 1.6.5 and dafs, I've been > getting the following errors, and it mostly stops being a fileserver. > Is this fixed i