info-cvs archive search

1. Re: CVS and NFS (score: 292)

Author: HIDDEN

Date: Sat, 10 Mar 2007 09:03:01 -0800

Hi Steve, There are many cases where NFS clients have opened a file on an NFS server and written to it and the text written to disk is not the same as the text the client was attempting to write. Par

/archive/html/info-cvs/2007-03/msg00038.html (6,456 bytes)

2. Re: CVS and NFS: Questions (score: 292)

Author: HIDDEN

Date: Thu, 9 Oct 2003 19:25:42 -0400 (EDT)

Derek Robert Price writes [about NFS-mounted repositories]: No, they're not. We've never had a report of a problem related to locking on NFS. No. NFS guarantees that mkdir() is an atomic operation, s

/archive/html/info-cvs/2003-10/msg00064.html (7,075 bytes)

3. Re: CVS and NFS (score: 288)

Author: HIDDEN

Date: Sat, 10 Mar 2007 17:49:15 -0500 (EST)

The short answer: yes, it's still relevant; and yes, you're risking NFS corruption. However, you're in the very low risk category right now -- your file server is a dedicated NAS appliance that shoul

/archive/html/info-cvs/2007-03/msg00040.html (5,655 bytes)

4. Re: CVS and NFS: Questions (score: 285)

Author: HIDDEN

Date: Thu, 9 Oct 2003 17:30:22 -0400 (EDT)

[...] No. There is a potential problem with locking across NFS, but it has never been reported as actually occurring in practice and, if it did, it would just result in a denial of service, not repos

/archive/html/info-cvs/2003-10/msg00060.html (6,494 bytes)

5. Re: CVS corruption or other? (score: 266)

Author: HIDDEN

Date: Wed, 27 Oct 2004 22:49:20 -0500

Thx VERY much for the response. One other question and I apologize, it's probably fairly basic. When I run the validate script, there were 2 results. 1. corruption of files in the Attic - should I be

/archive/html/info-cvs/2004-10/msg00318.html (6,473 bytes)

6. Re: CVS and NFS: Questions (score: 266)

Author: HIDDEN

Date: Thu, 09 Oct 2003 17:30:45 -0400

Many of the issues are related to locking. CVS uses a successful mkdir(lockdir) to prevent other processes from creating locks. As I understand it, caching issues in NFS clients can cause two process

/archive/html/info-cvs/2003-10/msg00062.html (6,668 bytes)

7. CVS and NFS (score: 260)

Author: HIDDEN

Date: Fri, 9 Mar 2007 14:57:29 -0800

The long question: I was investigating the best Windows CVS client for us to use, and noticed that every client seemed to have a problem dealing with Network Drives. Upon further investigation I noti

/archive/html/info-cvs/2007-03/msg00036.html (8,446 bytes)

8. Re: Understanding problems with NFS & CVS. (score: 260)

Author: HIDDEN

Date: Wed, 5 Sep 2001 17:19:22 -0400 (EDT)

[ On Wednesday, September 5, 2001 at 10:18:09 (-0700), Paul Sander wrote: ] Depends on what you man by "properly configured". SunOS-4.x was at first considered to be "properly configured" even when U

/archive/html/info-cvs/2001-09/msg00134.html (7,527 bytes)

9. Re: CVS repository corruption (score: 254)

Author: HIDDEN

Date: Tue, 02 Jan 2001 16:07:58 -0800

Hi Fran, I ran into the problem you described a while back (4-5 years ago, I think). At that time, I was using CVS on Solaris and the repository was accessed via NFS. I was able to repair the files i

/archive/html/info-cvs/2001-01/msg00016.html (7,398 bytes)

10. CVS and NFS: Questions (score: 253)

Author: HIDDEN

Date: Thu, 9 Oct 2003 13:38:27 -0700 (PDT)

Regarding an NFS mounted repository: We have a Unix server (dev30) with cvs version 1.11 loaded on it that is NFS mounted to a disk that contains our repository ( /cvs ). THIS IS THE ONLY SERVER THAT

/archive/html/info-cvs/2003-10/msg00059.html (6,233 bytes)

11. Re: CVS over NFS (score: 253)

Author: HIDDEN

Date: Thu, 09 May 2002 12:06:45 -0400

* Gianni Mariani Is the main problem locking? If so, would it help to place the locks on a non-NFS disk? Sure, assuming that all disk access to the NFS repository was from the same machine, but why d

/archive/html/info-cvs/2002-05/msg00187.html (7,100 bytes)

12. Re: CVS Best Practice: cvs in conjunction with nfs? (score: 249)

Author: HIDDEN

Date: Mon, 23 Mar 2009 09:49:27 -0400

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 wh

/archive/html/info-cvs/2009-03/msg00064.html (7,842 bytes)

13. Re: CVS, NFS Filesystem, and failover (score: 248)

Author: HIDDEN

Date: Mon, 8 Oct 2001 11:25:39 -0700

I have also personally experienced a situation with NetApp servers where under heavy load a rename(a,b) call became an unlink(b) call, which caused new committed data to be silently lost. It's been a

/archive/html/info-cvs/2001-10/msg00273.html (6,596 bytes)

14. Re: CVS, NFS Filesystem, and failover (score: 248)

Author: HIDDEN

Date: Mon, 8 Oct 2001 13:30:23 -0400 (EDT)

There have been lots of reports of repository corruption caused by interoperability problems between different NFS client and server implementations. The most common problem is missing data: the file

/archive/html/info-cvs/2001-10/msg00272.html (6,096 bytes)

15. Re: CVS repository corruption (score: 245)

Author: HIDDEN

Date: Tue, 2 Jan 2001 12:53:19 -0500

As I mentioned in private email. I would recommend moving away from using nfs to mount the repository so you could do work. Set it up in pserver mode( or rsh, or ssh ) and give it a try... If you don

/archive/html/info-cvs/2001-01/msg00005.html (6,714 bytes)

16. Re: Migrating CVS database and users from NFS to pserver (score: 241)

Author: HIDDEN

Date: Thu, 1 Aug 2002 13:46:37 -0400 (EDT)

[ On Thursday, August 1, 2002 at 10:02:59 (-0400), Martin d'Anjou wrote: ] Why don't you go all the way to SSH too? assuming you're using a new/different machine to host CVS: 0. install the new CVS s

/archive/html/info-cvs/2002-08/msg00008.html (7,161 bytes)

17. Re: Understanding problems with NFS & CVS. (score: 241)

Author: HIDDEN

Date: Wed, 05 Sep 2001 23:47:06 -0700

Yup, one particular 'NFS' configuration option that has caused problems was that UDP checksums were not enabled by all clients and/or servers that were trying to access the repository. This may allo

/archive/html/info-cvs/2001-09/msg00148.html (6,706 bytes)

18. DOC file corruption (score: 240)

Author: HIDDEN

Date: Thu, 10 May 2001 19:21:54 -0700

I believe that an archive in our repository is corrupt, and would like advice on how to possibly fix it, and how to prevent corruption in the future. This is a new installation. The server is cvs 1.1

/archive/html/info-cvs/2001-05/msg00377.html (4,764 bytes)

19. Re: CVS repository corruption (score: 239)

Author: HIDDEN

Date: Tue, 2 Jan 2001 13:52:44 -0500 (EST)

The problems you're experiencing are almost certainly due to NFS bugs in Linux and/or AIX which have now corrupted your repository, quite possibly beyond repair. This is why we always tell people to

/archive/html/info-cvs/2001-01/msg00007.html (5,244 bytes)

20. RE: CVS Best Practice: cvs in conjunction with nfs? (score: 235)

Author: HIDDEN

Date: Mon, 23 Mar 2009 20:58:00 +1100

Peter, Could be: A) you are lucky B) you haven't discovered the corruption yet C) you are less likely to observe the problems due to a particular software stack (as Larry explained) D) you were lucky

/archive/html/info-cvs/2009-03/msg00062.html (6,546 bytes)