Date: Thu, 10 Apr 97 10:38:21 PST From: kachun@zippo.com (Kachun Lee) To: dyson@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: NFS/mmap freeze in 2.2R Message-ID: <199704101748.KAA25163@dopey.pathlink.com> In-Reply-To: <5iism1$s6l@newsrv.zippo.com> References: <199704100622.XAA19967@newport.ece.uci.edu> from Steven Wallace at "Apr 9, 97 11:22:15 pm" <5iism1$s6l@newsrv.zippo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <5iism1$s6l@newsrv.zippo.com>, you say... > >> >> I have discovered how to freeze the system over an NFS mounted filesystem. >> If you map a file over NFS read/write and shared, write >> to the area in memory, and then have another program read that nfs file, >> the system will freeze. The freeze is kindof wierd though. >> It appears that the kernel is still running somehow. >> I can change the sysconts vty's but typing and all other processes >> are frozen and not running. >> >Sounds like a recursive VFS locking problem or somesuch. Thanks for the >report, and will look at it ASAP. > >John While you are at it, maybe, you want to check this out also. We noticed we have been getting these messages: ------------- Apr 8 23:21:12 lois /kernel: vnode_pager_getpages: I/O read error Apr 8 23:21:12 lois /kernel: vm_fault: pager input (probably hardware) error, P ID 11987 failure Apr 8 23:21:12 lois /kernel: pid 11987 (in.nnrpd), uid 7003: exited on signal 11 -------------- since 2.2R or later with our NFS mounted news servers. They appeared at the NFS clients during news was expiring at the NFS server. That leaded me to believe that the message was triggered when someone was reading an article while the NFS server removed it - both systems kept running though.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704101748.KAA25163>