On Tue, 3 Aug 2010 13:23:30 +0100 Jon Bramley <brammers@xxxxxxxxx> wrote: > I've posted the dmesg output with cifsFYI set to 7, for the failed cvs > update command here: > > http://paste.org/pastebin/view/21123 > > One strange thing I notice, is that at one point it seems to be doing > something with /home/jbramley/cvs_src/appserv/lib/ix86, but that folder is > not in any of my env vars (PATH, LD_LIBRARY_PATH etc.) so I can see no > reason for it to be looking there. Could this be some kind of inode > confusion on the cifs share? > *shrug* -- maybe... Without a clear description of what the actual problem is it's anybody's guess. All you've really told us so far is that cvs doesn't work right. We need to understand what's wrong at the system call level before we can really do much to help you. I'd not bother with debugging output and such at this point. You need to focus on the application. What's going wrong with it? Once you understand that, then we can look at what's happening in the kernel. -- Jeff Layton <jlayton@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html