From owner-freebsd-stable@FreeBSD.ORG Tue May 29 19:44:55 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3047B16A421 for ; Tue, 29 May 2007 19:44:55 +0000 (UTC) (envelope-from steve@netfirms.com) Received: from mh.netfirms.com (mh2.netfirms.com [66.46.53.2]) by mx1.freebsd.org (Postfix) with SMTP id 8929E13C45B for ; Tue, 29 May 2007 19:44:54 +0000 (UTC) (envelope-from steve@netfirms.com) Received: (qmail 26795 invoked from network); 29 May 2007 19:46:45 -0000 Received: from unknown (HELO gort.nfcorp.netfirms.com) (192.168.2.86) by 0 with SMTP; 29 May 2007 19:46:45 -0000 Received: by gort.nfcorp.netfirms.com (Postfix, from userid 1000) id 8036E178793; Tue, 29 May 2007 15:21:55 -0400 (EDT) Date: Tue, 29 May 2007 15:21:55 -0400 To: freebsd-stable@freebsd.org Message-ID: <20070529192155.GA19514@netfirms.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 From: steve@netfirms.com (steve) Subject: vnode_pager_putpages errors on 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 19:44:55 -0000 Howdy! I had this issue on 4.x, which is basically, I have machines that do cgi stuff for customers, and there is a local md device that is used as a tmp. When it fills the machine logs errors vnode_pager_putpages I/O error 28.. and the machine is unresponsive and needs to be power cycled. There is a previous thread on this issue http://atm.tut.fi/list-archive/freebsd-stable/msg19031.html and a subsequent patch for 4.x http://atm.tut.fi/list-archive/freebsd-stable/msg19288.html that I appled to 4.x and it solved the problem. Now that I have upgraded to 6.2, the problem has recurred, but the previous patch is no longer valid. Is there something wrong with the patch/solution given, and is there a solution for 6.2? thanx - steve