I now have 3 machines out of about 20 that have this problem. The problems
are always on the D: drive. On all 3 machines, the D: drive is the 2nd
partition of a RAID (mirrored) array. On one of them we removed the RAID,
and it still had a problem. We stopped using TortoiseSVN, and the problems
The basic problem is that subdirectories disappear from the directories
under Subversion's control, and it seems to only happen on the D: drive on
machines running Windows 2003 Server.
Has anyone had a similar problem?
The svnserver version is a few months old, and the clients are a few weeks
old, but there versions are supposed to be compatible (I'll post the exact
versions later today). If I remember correctly, Subversion is pretty good
about letting you mix old and new client and server versions, so I don't
think its that.
My personal suspcion is that the problem is either related to all the recent
Microsoft patches or to an unknown Subversion bug that only effects drive D:
on Windows 2003 Server machines.
We are still doing a lot of tests to try and determine exactly what is going
on. I will run a HD benchmark program on D: drives and see if I can get the
directories to disappear without using SVN.
On 1/4/06, Xn Nooby <firstname.lastname@example.org> wrote:
> I have a Windows 2003 Server that is using the latest Subversion and
> Tortoise client software to pull files from a dedicated server. Twice this
> machine had it's main Subversion-controlled directory get corrupted. Each
> time I have had to reboot and let it CHKDSK the drive. This most recent
> time the entire directory was lost, including uncommited files.
> Once the directory is corrupted, it cannot be browsed to using Windows
> Explorerer, even with TortoiseSVN removed. The error message is that the
> directory is inaccessible. From a DOS box, the directory cannot be CD'd in
> to. The DOS "copy" command was able to copy about 80% of the files.
> Are there any known problems with the Subversion and TortoiseSVN clients
> on Windows 2003 Server?
> This machine has RAID (mirrored) drives, so it is unlikely to be a
> physical media problem. We have other machines similarly configured, but
> this is the only one that is suffering from corruption problems. I do not
> think that simultaneous users are an issue (thought its possible since
> multiple people can log in remotely).
> I'm mostly wondering if there are any known issues regarding this. It's
> rare to have NTFS corruption, so something odd is going on.
Received on Wed Jan 11 18:15:08 2006