On 2 August 2010 18:14, Jeff Layton <jlayton@xxxxxxxxx> wrote: > > On Mon, 2 Aug 2010 16:56:10 +0100 > Jon Bramley <brammers@xxxxxxxxx> wrote: > > > Just checked on a colleagues machine, and uname -r reports 2.6.32-24-generic > > > > Also checked the dmesg on the Ubuntu 10.04 box: > > > > [ 964.362027] CIFS VFS: Autodisabling the use of server inode > > numbers on \\shared.openbet\shared. This server doesn't seem to > > support them properly. Hardlinks will not be recognized on this mount. > > Consider mounting with the "noserverino" option to silence this > > message. > > [ 964.368470] CIFS VFS: server 10.194.0.105 of type Samba 3.0.28a > > returned unexpected error on SMB posix open, disabling posix open > > support. Check if server update available. > > > > The exact same errors that I get appear, which leads me to believe > > that this in itself is not the cause of my issue. > > > > Any other ideas to debug further? > > > > Yes, I agree that the above warnings may have nothing to do with the > problem. We need to understand what the problem is. The strace shows > this: > > write(2, "cvs [update aborted]: cannot get"..., 78cvs [update aborted]: cannot get working directory: No such file or directory) = 78 > > ...but I don't see any system calls that returned -ENOENT. Maybe it > occurred in another thread or something? > > So I'm a little unclear as to what cvs is complaining about. It's quite > possible that it's ultimately a bug in cifs, but without more info I > really can't guess as to what the problem is. What we really need is a > description of the problem couched in terms of the system call > interface. > > -- > Jeff Layton <jlayton@xxxxxxxxx> 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 noticed, 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? Thanks, Jon -- 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
