From owner-freebsd-stable@FreeBSD.ORG Fri Oct 8 18:41:04 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23BC616A4CE for ; Fri, 8 Oct 2004 18:41:04 +0000 (GMT) Received: from arrow.wiznet.ca (arrow.wiznet.ca [216.138.223.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2CDB43D4C for ; Fri, 8 Oct 2004 18:41:03 +0000 (GMT) (envelope-from steve@nomad.lets.net) Received: from nomad.lets.net (H74.C220.tor.velocet.net [216.138.220.74]) by arrow.wiznet.ca (Postfix) with SMTP id C08AFD209 for ; Fri, 8 Oct 2004 14:41:02 -0400 (EDT) Received: (qmail 38143 invoked by uid 1008); 8 Oct 2004 19:47:43 -0000 Date: Fri, 8 Oct 2004 15:47:43 -0400 From: Steve Shorter To: stable@freebsd.org Message-ID: <20041008194743.GB38115@nomad.lets.net> References: <20041008184048.GA37831@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041008184048.GA37831@nomad.lets.net> User-Agent: Mutt/1.4i Subject: Re: vnode_pager_putpages errors and DOS? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2004 18:41:04 -0000 On Thu, Jan 01, 1970 at 12:00:00AM +0000, Steve Shorter wrote: > Howdy! > > FreeBSD 4-10 > > I have some machines that run customers cgi stuff. > These machines have started to hang and become unresponsive. > At first I thought it was a hardware issue, but I discovered in > a cyclades log the following stuff that got logged to the > console which explains the cause of the system hangs/failures. > > vnode_pager_putpages: residual I/O 65536 at 347 > vnode_pager_putpages: I/O error 28] > vnode_pager_putpages: residual I/O 65536 at 285] Aha! also at the same time I get in syslog /kernel: pid 6 (syncer), uid 0 on /chroot/tmp: file system full Whats happening? Can a full filesystem bring the thing down? Ideas? Fixes? thanx - steve > > Zillions of them. > > The only way to recover the machine is to power cycle > it. > > From what I can tell from google etc.. and someone elses > experience it is probably the consequence of someone filling > up /var/tmp or something. > > Should a non root user program be able to DOS > a machine like this? or What is the cause and/or fix for this? > > > thanx - steve > > > > > > > "The age of the Internet has a right to its own music." > > http://www.linuxsuite.org > > ----- End forwarded message ----- > >