rpc.lockd

[Sparrevohn, Thomas]

After changing my FS to UFS2 yesterday I saw strange behaviour from
rpc.statd and rpc.lockd - The statd process grew to 256MB in size. There are
memory leaks some where in the 5.0-Release with UFS2 that I did not see with
UFS1 - It seems that inactive pages are never reclaimed and on a 1GB system
during a make world I ended up with 8MB free.

-- Thomas

-----Original Message-----
From: omestre at freeshell.org [mailto:omestre at freeshell.org] 
Sent: 29 April 2003 17:05
To: freebsd-hackers at freebsd.org
Subject: rpc.lockd



 Hello,
 I'm having problems with rpc.lockd (nfs locks)...
 Now, i guess that i know "where is" the problem. I have one Linux box as my
NFS server to Linux and FreBSD 4.x machines, working fine.  I have some
FreeBSD 5.0 machines that do not work the locks. Looking at the log in the
Linux server, i have saw these messages:
kernel: lockd: bad cookie size 16 (only cookies under 8 bytes are
supported.)  Without 5.0 clients, these messages go out! So, how can i make
the rpc.lockd work like 4.x series? 
 The 5.0 lock protocol, i guess, is incompatible with linux ( kernel
2.4.20).  Thanks.  


---

_______________________________________________
freebsd-hackers at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"