Comment 60 for bug 680529

Is this just a problem with Windows Server 2008 shares?

I have 80 students in a class, all getting "lock was renamed into place, but now is missing!" consistently. (I'm using bazaar as part of a workflow to get them to download skeleton projects, and to submit their completed assignments. Each student has their own dedicated local branch, and their own dedicated parent repository where their submissions happen.)

All commits work fine from the command line, so I can confirm that we've only seen problems when using Bazaar Explorer.

But, even Bazaar Explorer works fine for some NTFS shares! Our domain has a mix of newer and older servers, and it seems to work fine if the local branches are hosted on Windows Server 2003, but fails if the students' home directories are on a Windows Server 2008. (We've tried turning the shared drive read cache settings on and off, but it doesn't seem to make any difference.)

So if you've had this Bazaar Explorer issue on Windows network shares, or if you have not had this issue and Windows shares work fine for you, please let me (or this bug list) know whether your evidence supports the conjecture that this is an error specific to the GUI tools (Bazaar Explorer) and only on Windows 2008 shares (ir later?).

Thanks - some confirmation of what we think we see might help us narrow it down.