On Tuesday, September 12, 2006 12:37:03 PM +0200 Jerry Lundström
<[EMAIL PROTECTED]> wrote:
Tom Keiser wrote:
The i/o timing characteristics of memcache/ramdisk are very different
than a physical disk. It's quite possible that these timing
differences are allowing you to hit a race condition in the cache
manager. Is there any way you can provide us with a kernel stack
backtrace for the process(es) which gets stuck in afs_cv_wait?
Alternatively, could you provide us with an fstrace dump leading up to
the deadlock?
If you give me hints how?
echo t > /proc/sysrq-trigger
Then extract the resulting output from /var/log/messages or whereever.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
