[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs not checkout in pwd, but some other strange place.
From: |
Todd Denniston |
Subject: |
Re: cvs not checkout in pwd, but some other strange place. |
Date: |
Mon, 04 May 2009 16:53:23 -0400 |
User-agent: |
Thunderbird 2.0.0.19 (X11/20081209) |
Troels Kofoed Jacobsen wrote, On 05/04/2009 07:14 AM:
Todd Denniston wrote:
Troels Kofoed Jacobsen wrote, On 04/29/2009 03:02 AM:
Hi all
Can anyone tell me what's going on?
I agree with Arthur, please provide
Version of CVS?
CVSROOT?
what is the actual message, or be very careful when 'sanitizing' it.
Note in the following I have only changed path names, host names, domain
names and IP addresses.
Version: 1.12.12 installed via opensuse or compiled manually.
CVSROOT=:pserver:@myhost.mydomain.dk:/usr/local/cvs_repos
but this is reproducible with others.
# pwd
/users/myuser/tmp
# cvs checkout
cvs [checkout aborted]: could not chdir to /indirect/data/myuser/tmp: No
such file or directory
# mount
knfs:/users on /indirect/users type nfs
(rw,soft,sloppy,addr=192.168.1.2,nfsvers=3,proto=tcp,mountproto=udp)
knfs:/mnt/local on /indirect/local type nfs
(rw,soft,sloppy,addr=192.168.1.2,nfsvers=3,proto=tcp,mountproto=udp)
knfs:/data on /indirect/data type nfs
(rw,soft,sloppy,addr=192.168.1.2,nfsvers=3,proto=tcp,mountproto=udp)
OK, now I see enough to cause a problem, even if it is not causing _this_
problem.
[man nfs]
when you mount nfs with 'soft'
If an NFS file operation has a major timeout then report
an I/O error to the calling program. The default is to
continue retrying NFS file operations indefinitely.
when you mount nfs with 'hard'
If an NFS file operation has a major timeout then report
"server not responding" on the console and continue
retrying indefinitely. This is the default.
[man mount]
"Mount options for nfs ...
soft ... Usually it just causes
lots of trouble."
CVS (and most other programs) expects 'hard' handling.
The appropriate compromise is 'hard,intr'.
I have seen much data loss/corruption with soft. For something that is read
only, it might be OK, but not for something that is writable in a network with
more than ~2 physical computers.
The following conversation might be of some interest.
http://linux.kernel.org/pipermail/autofs/2004-April/001119.html
http://linux.kernel.org/pipermail/autofs/2004-April/001120.html
http://linux.kernel.org/pipermail/autofs/2004-April/001121.html
# ls -l /users
lrwxrwxrwx 1 root root 15 2007-03-26 18:11 /users -> /indirect/users
I believe you are using an autofs, which mounts NFS file systems only
when they are needed, if the needed file system is already mounted it
works ok, if not it does not.
Not really. All needed filesystems are mounted!
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter