[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS, NFS Filesystem, and failover
From: |
Philip Lijnzaad |
Subject: |
Re: CVS, NFS Filesystem, and failover |
Date: |
08 Oct 2001 15:30:34 +0100 |
> I've heard it mentioned on this newsgroup that mixing NFS with CVS is a bad
> idea.
Running CVS with the repository and/or the local working copies on
NFS-mounted disks is fairly common, I would say. But it won't be immune from
general NFS problems, of course.
I once tracked such a problem down to a
$CVSROOT/SomeModule/Some/Sub/Dir/.nfsSomeFilelock still lying around;
removing it manually solved it. I've seen similar things in user directories.
> The idea in mind is a CVS server has a repository that is NFS mounted from
> an external storage system.
> (CVS server) (Backup CVS server)
> |
> |
> [NFS]
> |
> |
> (Server exporting)
> (NFS /cvs filesystem)
> The goal here is to have;
> 1. A backup CVS server, in case the first one fails.
Mmm ... I'm not sure how this should work, I can imagine that you can get
concurrency of locks?
> 2. Disk storage from an external source (such as a NetApp system), that hase
> high capacity, is used for several different storage systems, and can
> centralize backups.
yes. For e.g. ext or pserver access, it would be nice to have direct disk
access, though.
> 3. Possible to have backup CVS server come on line if the primary CVS server
> fails (mounting the NFS system, and taking over the IP address of the first
> machine)
Again, locks that get stuck may become a problem.
Philip
--
The mail transport agent is not liable for any coffee stains in this message
-----------------------------------------------------------------------------
Philip Lijnzaad, address@hidden European Bioinformatics Institute,rm A2-08
+44 (0)1223 49 4639 Wellcome Trust Genome Campus, Hinxton
+44 (0)1223 49 4468 (fax) Cambridgeshire CB10 1SD, GREAT BRITAIN