Hi Pavel, Thanks for getting back to me.
After trying many things to no avail I had changed the VisualSVN service to run under Administrator as a last resort to simply see if it solved the issue. I am however happy to report I have solved (or at least, identified) the problem. The (software based) raid solution my server is running is FlexRAID: it provides redundancy through parity-snapshots and also performs drive pooling ie. it presents a collection of arbitrary disks as a single logical volume. It was on this volume that I set my repository folder - the idea being it would be protected by parity like the rest of my data. I am unsure whether the fault lies within apache or it's down to the FlexRAID driver but whatever the case, this setup resulted in a lot of failed commits. I have since moved my repositories folder to a physical disk the OS controls directly and everything is working as it should. In terms of back up I plan on using either svnsync or hotcopy to replicate the repository on the RAID pool. Hopefully this info might benefit some other people down the line. cheers, H -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To post to this group, send email to visualsvn@googlegroups.com. To unsubscribe from this group, send email to visualsvn+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/visualsvn?hl=en.
