Hello,
I'm running a simple "stress test" on OpenAFS 1.4.11 (Red Hat 5.4 -
2.6.18-164.el5), a shell script that does a number of "cp" and "cmp" in
parallel for several days, but nothing sophisticated.
On several nodes I got plenty of "all buffers locked" messages on the console.
In certain cases subshells of that shell-script segfault.
I haven't yet had time to dig deeper into this, after finding that the message
comes from afs_buffer.c (and deserves an "afs:" and a "\n"!) and google for
once "not being my friend" I thought I'd ask first. Has anybody run into this?
(slabinfo shows e.g. 1579993 for afs_inode_cache. Is that big? About same size
as dentry_cache.
My plan is to try add a traceback to afs_buffer.c, and eventually try with
1.4.8+security patch which we still run on a big scale here. Any other ideas?)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rainer Toebbicke
European Laboratory for Particle Physics(CERN) - Geneva, Switzerland
Phone: +41 22 767 8985 Fax: +41 22 767 7155
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
