Lots of people don't have the problem, and lots do (e.g. http://schleichermann.wordpress.com/2009/12/09/svn-tortoisesvn-cant-move-the-file-or-directory-is-corrupted-and-unreadable-windows-7/<http://schleichermann.wordpress.com/2009/12/09/svn-tortoisesvn-cant-move-the-file-or-directory-is-corrupted-and-unreadable-windows-7/#comment-100>). It affects me particularly, probably because my processor is fast enough to allow the virus scanner to catch up with the temporary files. Surely keeping the temp files open with exclusive access would solve the problem? It's hugely frustrating - usually it takes me three or four attempts punctuated by cleanups to get an update or check in.
By the way, this is the same issue as reported by Khash Sajadi ( http://svn.haxx.se/tsvnusers/archive-2009-09/0366.shtml). On Thu, Jan 14, 2010 at 5:18 PM, Dave Purrington <dave.purring...@gmail.com>wrote: > FWIW, I'm on Windows 2008 Server R2 (the server version of Windows 7) with > a large repo. I have Windows Search enabled as well as virus scanning. The > only time I have seen this behavior is running Filemon or Procmon during svn > operations. > > > On Thu, Jan 14, 2010 at 4:59 AM, David Turner <dktur...@gmail.com> wrote: > >> From the TortoiseSVN lists: >> >> A few people have raised this: a check-out on Windows 7 often fails >> because entries is unreadable. This is caused by antivirus software and/or >> Windows indexing services competing for file locks. It's fairly easy to >> reproduce with a large repository on Windows 7 if you have antivirus >> software and are checking out into an indexed folder. >> >> Obviously those of us in a corporate environment don't have the option >> of disabling our antivirus software. >> >> Is it possible to keep entries open with exclusive access for the >> duration of the move from tmp/entries to entries? >> > >