I’ve hit this a couple of times recently, but it wasn’t until last night that I had cause (and time) to do a bit of research into it.
It occurs when you’re adding a large amount of files to Subversion, and appears to be due to the disk indexing process and/or anti virus. Some people’s experiences vary, in my case it seemed to be excluding my repository locations from indexing which solved it, but others seem to have fixed it by excluding their code locations from being scanned by their AV software.
The other side affect is that it triggers a chkdsk when you restart – I’d not linked the chkdsk scans to the Tortoise error, partly because I usually sleep my machine, and only reboot once every couple of weeks. I’d still noticed the chkdsk scans and thought “Hmmm", so it’s nice to know/hope they’ll be going away now.
Here’s a couple of links with more info:
Link: 64-bit TortoiseSVN on Windows 7 says “file or directory is corrupted and unreadable” then runs chkdsk
Link: SVN: TortoiseSVN Can’t Move .. The file or directory is corrupted and unreadable (Windows 7)
I mentioned a repository corruption issue in a previous post, and it’s interesting to note that I recognised the revno which was corrupted – it was from a session where I tried to check in a large amount of files, and received this error message. It may just be a co-incidence, but I found it slightly eerie.
Tags: SubVersion, Windows