find stuck in state "clock"
dillon at apollo.backplane.com
Sun Aug 28 11:20:35 PDT 2005
:while looking around on chlamydia why it is so slow I found a dozen
:find(1)s stuck in state "clock", and all periodic scripts etc dangling
:on that. Dmesg tells me:
:Aug 28 03:01:04 chlamydia kernel: [diagnostic] cache_lock: blocked on
:the system is
:DragonFly chlamydia.fs.ei.tum.de 1.2.2-RELEASE DragonFly 1.2.2-RELEASE
:#3: Tue Jun 21 23:57:56 CEST 2005
:root at xxxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/CHLAMYDIA i386
:Has this been fixed since?
I believe it was fixed. I'm not entirely sure if it was MFC'd but
I think it was.
:Talking of -RELEASE, Matt, do you intend to MFC some more fixes? Just
:curious because the last commit (4 weeks ago) to subvers stated
:NOTE: As of this commit there are several more bug fixes under test,
:including an important softupdates bug fix, and the release subversion
:will likely be bumped again in ~2 weeks after testing has been completed
:on those fixes.
There are a bunch. I think the softupdates bug that comment is refering
to was fixed in -RELEASE (184.108.40.206), on August 5th, but we haven't
slipped the tag yet on it. There are a few more bug fixes, such as the
one I just fixed for NFS servers, and one currently under test for
ffs_balloc(), which I want to throw in before I bump the sub version
Once every one or two months I usually do a run through the CVS logs
to determine what to MFC, MFC it, then bump the subvers on the release
More information about the Bugs