On Thu, Dec 1, 2011 at 9:44 AM, Jeff Layton <jlayton@xxxxxxxxx> wrote: > On Wed, 30 Nov 2011 15:25:01 +0100 > Johannes Thrän <johannes.thraen@xxxxxxxxxxxxxx> wrote: > >> Hi all, >> >> I reported this before here, it somehow went under. So I'll try again: >> >> When I open a file which is located on a cifs-mounted windows share >> with vim, vim will after some time always report the file as having >> changed upon saving, regardless whether it has actually changed or >> not. >> >> I reported this also to the vim maintainer who told me, there he >> doesn't know of a similar problem with samba. Ergo it's probably a >> problem with cifs. >> I work on a daily basis with mentioned setup, so I would be vary glad >> to help resolve it. >> >> mount.cifs -v gives 4.5, I use kubuntu 11.04 and vim 7.2 >> > > Unfortunately, this sort of report doesn't help us to help you very > much. I have no idea what vim is actually complaining about when it > says that the file has changed. > > As it's a kernel filesystem, it primarily deals with userspace code via > system calls. If you can phrase your problem in that context then > that would help. We'd need to know what vim is actually looking at to > detect that the file has changed. Is it the mtime? > > -- > 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 > yes, that would be useful. I just tried with vim 7.2.22, cifs version 1.76 against a Windows 2003 server and after two minutes of opening a file and while closing, no errors or messages. What is the exact error message by vim? And how long is "sometime"? A trace data (strace, wireshark, tcpdump) obtained while encountering/recreating the problem would help. -- 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
