From owner-freebsd-fs@FreeBSD.ORG Wed Sep 15 15:30:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC0BD106564A for ; Wed, 15 Sep 2010 15:30:09 +0000 (UTC) (envelope-from ecrist@claimlynx.com) Received: from na3sys009aog102.obsmtp.com (na3sys009aog102.obsmtp.com [74.125.149.69]) by mx1.freebsd.org (Postfix) with ESMTP id 931C58FC2A for ; Wed, 15 Sep 2010 15:30:09 +0000 (UTC) Received: from source ([209.85.213.173]) by na3sys009aob102.postini.com ([74.125.148.12]) with SMTP ID DSNKTJDmgBTOuSsuZjBLnWQECLwRhWAFf7Tz@postini.com; Wed, 15 Sep 2010 08:30:09 PDT Received: by mail-yx0-f173.google.com with SMTP id 7so127100yxs.4 for ; Wed, 15 Sep 2010 08:30:08 -0700 (PDT) Received: by 10.151.14.15 with SMTP id r15mr2125501ybi.75.1284562899659; Wed, 15 Sep 2010 08:01:39 -0700 (PDT) Received: from swordfish.ply.claimlynx.com (mtka.claimlynx.com [74.95.66.25]) by mx.google.com with ESMTPS id m11sm2316194ybn.4.2010.09.15.08.01.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 15 Sep 2010 08:01:38 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1081) From: Eric Crist Date: Wed, 15 Sep 2010 10:01:36 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.1081) Cc: Thomas Johnson Subject: NFS nfs_getpages errors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eric Crist , Thomas Johnson List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2010 15:30:09 -0000 Hey folks, We've got 4 servers running FreeBSD 8.1-RELEASE which PXE boot with NFS = root. On these machines, we run proftpd and apache 2.2. Over the past = couple weeks, we've seen a ton of errors as follows: Sep 14 20:28:59 lion-3 proftpd[31761]: 0.0.0.0 = (folsom-1-red.claimlynx.com[216.17.68.130]) - ProFTPD terminating = (signal 11)=20 Sep 14 20:28:59 lion-3 kernel: nfs_getpages: error 1046353552 Sep 14 20:28:59 lion-3 kernel: vm_fault: pager read error, pid 31761 = (proftpd) Sep 14 20:28:59 lion-3 kernel: Sep 14 20:28:59 lion-3 proftpd[31761]: = 0.0.0.0 (folsom-1-red.claimlynx.com[216.17.68.130]) - ProFTPD = terminating (signal 11)=20 Sep 14 20:28:59 lion-3 kernel: nfs_getpages: error 1046353552 Sep 14 20:28:59 lion-3 kernel: vm_fault: pager read error, pid 31761 = (proftpd) Sep 14 20:28:59 lion-3 kernel: pid 31761 (proftpd), uid 0: exited on = signal 11 These, in this case, occurred on three of the four machines until = midnight after which all three of the machines had proftpd exit on = signal 11. The message above was for child processes. At midnight, the = logfile rotated, and newsyslog sent singal 1 to the parent process, = which I think finally finished it off. The fourth machine remained = running and did not display these messages. The number following 'nfs_getpages: error' changes for each cycle and = I'm not certain if any of them repeat. root@lion-3:~-> uname -a FreeBSD lion-3.claimlynx.com 8.1-RELEASE FreeBSD 8.1-RELEASE #2: Mon Aug = 2 12:50:40 CDT 2010 = root@jaguar-1.claimlynx.com:/usr/obj/usr/src/sys/GENERIC-CARP amd64 --- Eric F Crist System Administrator ClaimLynx, Inc (952) 593-5969 x2301