Re: Can subversion corrupt an NTFS drive?
From: Samay <getafix123_at_hotmail.com>
Date: 2006-01-12 22:34:04 CET
We use svn client installations (tsvn 1.2.6 client, https access to server), on win2k3 server, win2k3_x64 server on Dell PowerEdge 1850(8 GB RAM, EM64T), 1750 (4 GB RAM) grade servers with SCSI disks (2x73 GB 15kRPM) in Raid-1, and havent yet encountered this issue as in drive/NTFS level corruptions on both first (OS) & second, third (Data) partitions.
I suggest that you also advise your IT staff to look for BIOS Firmware or OS driver related issues under excessive NTFS kind of IO. (remember SVN working copy are expensive in terms of directory and space usage). See if you can reproduce this problem on a totally different hardware (different hardware configuration, different raid controller, but similar SCSI RAID-1 setup) in your environment.
..regards,
We are still having problems with machines getting corrupted subversion directories. We are using Ver 1.2.3 (r15833) on both the clients and server (running svnserve). The corruption shows up as missing and inaccessible subversion-controlled directores. We do a checkdisk and it fixes the corruption for a few days. This is on Windows 2003 Server machines. It only seems to effect the 2nd partition on a drive. Most of the machines had RAID mirrored drives. The errors show up in the WIndows Event Log as 'ntfs' errors.
It's hard for me to believe that Subversion would do anything that would corrupt an NTFS paritition, and its hard for the computer support guys to believe it's a hardware problem (since most of the drives are mirrored). I'm beginning to think their is an obscure Windows bug that Subversion is getting tripped up by.
Some users use a SUBST drive letter for their D: drive, instead of another partition, and their systems work fine.
Has anyone had any experiences similar to this?
Is anyone using Windows 2003 Server on their client machines, with a 2nd partition, and has it worked?
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.