Whoops, spelled [email protected] incorrectly.
-Ben
---------- Forwarded message ----------
Date: Sat, 29 Oct 2011 16:20:43 -0400 (EDT)
From: Benjamin Kaduk <[email protected]>
To: Simon Wilkinson <[email protected]>
Cc: [email protected], OpenAFS Bug Reports via RT <[email protected]>
Subject: Re: [rt.central.org #130282] "all buffers locked" on master
On Sat, 15 Oct 2011, OpenAFS Bug Reports via RT wrote:
Any kind of significant use (svn cleanup or svn up have been my main
triggers)
leads to "all buffers locked" spew on the console and an unusable client, on
my
freebsd system.
I believe Derrick has reproduced on ukernel.
Pulling some older git checkouts makes it seem that it has been around for
several months at least, though master has not always been directly
build/loadable on freebsd so it's hard to quickly bisect.
1.6 seems unaffected.
I finally got around to doing the bisection on this, which points to
0284e65f97861e888d95576f22a93cd681813c39 as the first bad commit.
commit 0284e65f97861e888d95576f22a93cd681813c39
Author: Simon Wilkinson <[email protected]>
Date: Wed Apr 27 14:24:56 2011 -0400
dir: Explicitly state buffer locations for data
I don't see anything in that commit that would make the bug obviously specific
to FBSD/UKERNEL ... is anyone else seeing this 'all buffers locked' issue on
master?
My test case is running 'svn up' on the FreeBSD source tree (a ~1.6G checkout).
-Ben
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
