NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/32318: NFS client or server hang



On Fri, Dec 16, 2005 at 07:00:01PM +0000, Manuel Bouyer wrote:
> >Number:         32318
> >Category:       kern
> >Synopsis:       NFS client or server hang
> >Confidential:   no
> >Severity:       serious
> >Priority:       medium
> >Responsible:    kern-bug-people
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Fri Dec 16 19:00:01 +0000 2005
> >Originator:     Manuel Bouyer
> >Release:        NetBSD 3.0_RC3
> >Organization:
> >Environment:
> System: NetBSD chassiron.antioche.eu.org 3.0_RC3 NetBSD 3.0_RC3 (CHASSIRON) 
> #0: Sat Nov 26 15:11:16 CET 2005 
> bouyer%pop.lip6.fr@localhost:/local/pop1/bouyer/tmp/sparc/obj/local/pop1/bouyer/netbsd-3/src/sys/arch/sparc/compile/CHASSIRON
>  sparc
> Architecture: sparc
> Machine: sparc
> >Description:
>       Setup: I get mail from various pop3 server via fetchmail and
>       deliver to local folders (mbox format) via procmail, the folders are
>       stored on a NFS server.
>       fetchmail/procmail run on a x86 box (celeron 500) running a months-old
>       current:
> NetBSD rochebonne.antioche.eu.org 3.99.7 NetBSD 3.99.7 (ROCHEBONNE) #1: Tue 
> Aug  9 23:54:57 CEST 2005  
> bouyer%pop.lip6.fr@localhost:/local/pop1/bouyer/tmp/i386/obj/local/pop1/bouyer/current/src/sys/arch/i386/compile/ROCHEBONNE
>  i386
>       The NFS server is a sparc IPX (40Mhz sparcv7).
> 
>       Problem: from time to time, the process accessing the files on
>       the NFS server hang. This usually happens when the client does
>       2 concurent accesses to the mailboxes (e.g. reading a mailbox
>       with mutt while procmail tries to deliver a mail to this mailbox).
>       I've seen this also before the 3.0 branch was cut, with the NFS server
>       running 2.0 or 2.1. I've never noticed this when the server was running
>       1.6.2 (it started happening when the server got upgraded).

I didn't see this since I upgraded the server to 4.99.62 (from 4.99.20 or
so), neither during normal usage nor when trying explicitely to reproduce it.
It's still be nice to have it fixed in netbsd-3 and netbsd-4, but at last
this seems to have gone in current, and hopefully it won't show up again in
netbsd-5 :)

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index