Bug#184157: libc6: Locking problems over NFS
At Mon, 10 Mar 2003 15:44:47 +0100,
Vincent Bernat wrote:
> OoO En ce début d'après-midi ensoleillé du lundi 10 mars 2003, vers
> 15:30, GOTO Masanori <gotom@debian.or.jp> disait:
>
> >> /proc/mounts reports :
> >> neo:/home /home nfs rw,v3,rsize=8192,wsize=8192,hard,udp,lock,addr=neo
>
> > Which machine did you upgrade? NFS server? NFS client?
>
> NFS client.
Interesting behavior. NFS client uses lockd to contact NFS server's
lock manager as kernel thread. On the other hand glibc is on the
userland, and issues lock funtion into kernel. So I wonder why
upgrading libc6 causes such problem. It's hard to make nfs bad with
upgrading glibc...
You may upgrade a lot of packages at the same time, especially nfs
related package?
> > Was this problem still appeared after your system reboot?
>
> Not tried yet, it is a bit difficult to reboot it. I can do it at the
> end of the week. I will take you in touch about this.
Please do that.
> > If you upgrade your nfs server, your nfs server and lock manager is
> > kernel's ?; nfs-kernel-server is installed?
>
> The server is kernel one, so with kernel server.
>
> >> Kernel: Linux lucas 2.4.20-lucas.3 #1 Tue Feb 11 14:22:16 CET 2003 i686
>
> > Is your kernel your original version? Pure 2.4.20 without any
> > patches?
>
> The client is pure 2.4.20 without any patch, compiled from official
> kernel source. The server is a 2.4.20 patched with Trond patches.
Hm, so the client seems clean...
Regards,
-- gotom
Reply to: