NFS file locking with SuSE 8.2 client
Bob Vickers <[email protected]>
| Newsgroups | gmane.linux.admin.managers |
|---|---|
| Message-ID | <[email protected]> |
Dear All,
Today I upgraded a machine from SuSE 8.0 to SuSE 8.2 and galeon stopped
working. Galeon tries to start gconfd-2 and this fails; gconfd-2 also
fails if you try and start it by hand.
The message in the log is
gconfd (zmac089-13318): Failed to get lock for daemon, exiting:
Failed to create or open '/home/ugrads/xxxxxxx/.gconfd/lock/ior'
If I run strace on gconfd-2 I see
open("/home/ugrads/xxxxxxx/.gconfd/lock/ior", O_RDWR) = 6
fcntl64(6, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1
ENOLCK (No locks available)
I believe this an NFS locking problem. Galeon works if the home directory
is on a local disc, but not if it is on an NFS file system. It fails with
two different NFS servers: one of them SuSE Linux 8.0, one of them Tru64
Unix 4.0G. Neither server has changed recently.
Does anyone know of recent NFS client changes that might have affected
locking? And are there any other tests I can try to confirm whether or not
locking works at all or whether it is just gconfd that is affected?
rpcinfo reports (on the client)
/usr/sbin/rpcinfo -p localhost | grep lock
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
I'm rather stumped: any ideas gratefully received.
Bob
==============================================================
Bob Vickers [email protected]
Dept of Computer Science, Royal Holloway, University of London
WWW: http://www.cs.rhul.ac.uk/home/bobv
Phone: +44 1784 443691
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers-35TzE1X9F6582KRnZfj+bdi2O/[email protected]
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers