Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
We are using :pserver: (as we have some MAC and Linux clients) I agree that this looks like a HDD problem, but any HDD errors should be reported by the OS and they are not. I am wondering if buffer overflows inside CVSNT may be the cause. Corruption occurs on very large operations. i.e. while tagging 5,000 files, 3 of them get corrupted. There may also be other users performing operations at the same time. I sent out an email earlier describing the tagging operation timing out because another user was performing a lengthy operation at the same time. This is the main reason we set up a 2nd server and split the database. Also, the reason why I have 2 different versions of CVSNT is to test the current release. If all goes well :) I'll then upgrade the old one. Randy McCharles SMART Technologies Inc. Senior Software Developer Tel. 403.802.3347 Fax 403.229.2531 randymccharles at smarttech.com http://www.smarttech.com Bringing people and ideas together.(tm) -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Glen Starrett Sent: Thursday, December 22, 2005 7:24 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: RCS corruption during tagging Randy McCharles wrote: > The older 2.0 server has hard drives set up the same way, but is a Windows 2000 server. > These same large projects were tagged using the same scripts while on the old server, without the RCS corruption. It is only after moving them to the new server that the problem started. It "looks" like a bug in 2.5.02 that was not in 2.0.51 > However, since the hardware and OS have also changed, who knows... I would recommend either upgrading the old server to 2.5.02 or downgrading the new one to 2.0.51 so you can rule out CVSNT (or at least the change in CVSNT version) as the culprit. In my experience, overwritten files is a sign of a bad HDD. Assuming you aren't using :local: protocol across a network link (look for a network drive letter anywhere in your CVSROOT), I would guess hardware as the most likely cause. Regards, -- Glen Starrett _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs