From owner-freebsd-hackers Mon Nov 18 19:56:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA11800 for hackers-outgoing; Mon, 18 Nov 1996 19:56:30 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA11793 for ; Mon, 18 Nov 1996 19:56:27 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id VAA07278; Mon, 18 Nov 1996 21:56:15 -0600 (CST) Message-Id: <199611190356.VAA07278@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Michael Smith cc: hackers@freebsd.org Subject: Re: vnode_pager_input: I/O read error (2.1.5) In-reply-to: Your message of Tue, 19 Nov 1996 12:08:53 +1030. <199611190138.MAA25521@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Nov 1996 21:56:14 -0600 From: Chris Csanady Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Chris Csanady stands accused of saying: >> This is bad. Im concerned that this will not be fixed for 2.2 since I have >> seen similar messages in 3.0. It would be really nice to have a fix, and if >> anyone has something that I may try, I would really apreciate it. > >It's not likely to be fixed if it is truly the hardware error that it >appears to be. As it happens on any of our 16 (identical) machines, this is not likely. > >> Here are the error messages that are repeated thousands of times: >> >> Oct 16 11:04:09 d /kernel: vnode_pager_input: I/O read error >> Oct 16 11:04:09 d /kernel: vm_fault: pager input (probably hardware) error, PID >> 2531 failure >> Oct 16 11:04:09 d /kernel: vnode_pager_input: I/O read error > >Where are the error messages from the device driver? What are you swapping >on? Are you using NFS for either swap or your binaries? Swap is local, while all binaries and home dirs are mounted over NFS from an Irix 6.2 server. I've seen this error from a 2.1.5 server as well though. Our network is fast and very rarely saturated, so I do not believe that it would actually lose contact with the server unless its a server problem. However the same thing works from our SGI cluster, so I would not think that the case. We will be installing patches this friday, one of which i think is NFS related, so I will check that again though. > >> Chris Csanady > >-- >]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ >]] Genesis Software genesis@gsoft.com.au [[ >]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ >]] realtime instrument control. (ph) +61-8-8267-3493 [[ >]] Unix hardware collector. "Where are your PEZ?" The Tick [[