Thanks for davfs, it's cool.
I use jungledisk with davfs2 v1.1.2 and coda on (a
modified) FC5 system with Linux kernel 2.6.18.
Mount.davfs frequently gets into an infinite loop in
which (according to strace) it does nothing but call
access(..., F_OK) on files in its cache over and over.
It appears to traverse a long list of cache files and
On closer inspection, it looks like the list it's
iterating over changes over time. Looking at my strace
output, a particular file appears on line 1, then again
on line 2193, then again on line 4244, then 6389, then
8346. The deltas in each case are 2192, 2051, 2145,
1957. Perhaps this reflects the (slow) rate at which
jungledisk uploads drain out of davfs2's cache? In any
case, even if this apparent infinite loop is not
actually infinite (because eventually the entire cache
will drain), it still shouldn't race repeatedly through
all these access() calls, pinning my CPU at 100%.
I'm a software engineer and am available to help debug
this with a little guidance.
Log in to post a comment.