On Mon, 22 Jun 2009, Christian Kujau wrote: > On Mon, 22 Jun 2009, David Howells wrote: > >> [ 399.332346] [<ffffffff810da03a>] ? ext3_truncate+0x26a/0x9e0 > > > > Can you try the attached patch, please? > > The patch helps, I think. Without this patch I was able to reproduce > this very quickly, just running "grep -lr foo /share/nfs" was enough to > trigger the backtrace. With this patch, grep is still running (and > utilizing cachefiles) but no warnings so far. Unfortunately, now the system just freezes when doing *a lot* of read operations on the NFS share (grep -r foo again). I don't know if it's related to your patch or something else, debugging is kinda hard at the moment, as it's a Xen DomU (no netconsole; serial redirection magic still not working), it'll take me a while to figure out what's going on here. FWIW, I'm able to compile kernels over this very same (readonly) NFS share, only "grep -r" was able to trigger the freeze. Thanks, Christian. -- BOFH excuse #323: Your processor has processed too many instructions. Turn it off immediately, do not type any commands!! -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
