Hi, Goel, Von: Goel, Kapil [mailto:kapil.g...@fiserv.com] > > > Stripping is alternative, but how repair the corrupted revision or what > > > is the root cause to further stop corruption in other repos? > > > > Repository corruption is very unusual in Subversion. The most likely > > causes are: > > - The repository is running on a network file system or similar storage > > which does not properly implement synchronization / locking. > > - Hardware defect (defective RAM in the server, flipping bits on the > > cable).> > How we will identify Hardware issue , as diagnostics run by HW vendor > didn't reported any issue on Hardware. > > Repos are on Dedicated server hardware of Dell Poweredge R710
It depends on your BIOS/Firmware and the OS. The first thing you should ensure is that you use Memory with ECC enabled. In the system management interface, there should be some log showing you about ECC corrected errors (or similar) - if this number is greater than 0, your memory is defect. Also, you could run tools like memtest86 - they find most memory errors which are not found by the POST. Of course, checking the SMART data for the hard disks is on the list, too. And I remember that some of the earlier SSDs shipped with borked firmware leading to data loss. However, I'm not the specialist for finding hardware defects (our sysadmins take care for that), and this is not the best place to find answers for that subject. Best regards Markus Schaber -- ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
