[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Best Practice: cvs in conjunction with nfs?

From: Todd Denniston
Subject: Re: CVS Best Practice: cvs in conjunction with nfs?
Date: Mon, 23 Mar 2009 09:49:27 -0400
User-agent: Thunderbird (X11/20081209)

Peter Toft wrote, On 03/23/2009 02:28 AM:
On Thu, 19 Mar 2009, Kenneth Wolcott wrote:
Hi guys

I have been using CVS with NFS for many years with SSH as a bearer in a
multi-country setup for a large telecom - I have not seen any problems.
Only problem seen has been lost lock files once in a while, which had to be removed. And we have had our fair share of network trashing - as anyone else has from time to time. Our bottleneck has not been cvs for sure.
Our NFS servers are netapp boxes.

So the other replies in the same thread puzzle me a bit.

So have you ran validate_repo (or check_cvs, if you're using 1.11) [As Larry suggested] lately?

There may be corruption lurking somewhere in your repo that you just have not noticed... My memory may be failing me, but many of the times that I have seen NFS corruption, either personally or on this list, it was in the later parts of the file, i.e., after the current version... So you would not see the corruption unless you tried to check out an older version.

validate_repo|check_cvs may not be perfect, but they look for the usual suspects of problems.

After the first detection, I set our server up to run that script in a cron job so I could catch the faults before we rotated over the last good backup before the corruption. Fortunately we moved to having the cvs server processes run on the file server, and I have not had to ware that tee shirt out for ~5 years now.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]