* file locking error (37!) NFS problem
@ 2003-09-17 15:08 Bernhard Busch
2003-09-17 15:36 ` Trond Myklebust
0 siblings, 1 reply; 2+ messages in thread
From: Bernhard Busch @ 2003-09-17 15:08 UTC (permalink / raw)
To: nfs
Hello NFS Experts
I upgraded a NFS Server from Suse 8.0 to Suse 8.1.
If i use the EMAN program (Electron Image Processing Program, cluster
version) from
a client with Suse8.0 (the data files are on the fileserver) , i get
the error message
file locking error (37!) NFS problem
and the application crashes.
Under Suse8.0 (file server) everything is working well.
On the fileserver with Suse8.2
the application also crashes.
Many thanks for every help.
Sincerely
Bernhard Busch
--
Dr. Bernhard Busch
Max-Planck-Institut für Biochemie
Rechenzentrum
Am Klopferspitz 18a
D-82152 Martinsried
Tel: +49(89)8578-2582
Fax: +49(89)8578-2479
Email bbusch@biochem.mpg.de
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: file locking error (37!) NFS problem
2003-09-17 15:08 file locking error (37!) NFS problem Bernhard Busch
@ 2003-09-17 15:36 ` Trond Myklebust
0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2003-09-17 15:36 UTC (permalink / raw)
To: Bernhard Busch; +Cc: nfs
>>>>> " " == Bernhard Busch <bbusch@biochem.mpg.de> writes:
> Hello NFS Experts I upgraded a NFS Server from Suse 8.0 to Suse
> 8.1.
> If i use the EMAN program (Electron Image Processing Program,
> cluster version) from
> a client with Suse8.0 (the data files are on the fileserver) ,
> i get the error message
> file locking error (37!) NFS problem
*IF* the '37' is actually the error code returned by the kernel (in
which case it seems stupid that they don't use 'perror()' to report it
in standard format, but whatever...), then that would just be -ENOLCK
(i.e. the lock failed).
Check that your new server is not firewalling the port that is being
used by lockd. ('rpcinfo -p' will tell you which port that is).
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-09-17 15:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-17 15:08 file locking error (37!) NFS problem Bernhard Busch
2003-09-17 15:36 ` Trond Myklebust
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.