From owner-freebsd-questions@FreeBSD.ORG Sun Mar 13 20:44:43 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C1D616A4CE for ; Sun, 13 Mar 2005 20:44:43 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id C690A43D1F for ; Sun, 13 Mar 2005 20:44:42 +0000 (GMT) (envelope-from john.destefano@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so1471554rnf for ; Sun, 13 Mar 2005 12:44:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=gaAgqDAB5wWu94lYJh92Zx3wYrikUeJBX4gag027Lf78HHlOehfnrrDS1UcMaJ3zUVTgGWcl+/yoYAdU1BeSDr1jMs2U2q5KH16WvRK2AHXiOlaoBH6Ez+eObu8ODwe5qKbp4niMpSsbVLf/U4N2IqtM3F3Y4OYcI2Nnjryzqn0= Received: by 10.38.15.17 with SMTP id 17mr851603rno; Sun, 13 Mar 2005 12:44:32 -0800 (PST) Received: by 10.38.97.55 with HTTP; Sun, 13 Mar 2005 12:44:32 -0800 (PST) Message-ID: Date: Sun, 13 Mar 2005 15:44:32 -0500 From: John DeStefano To: freebsd-questions@freebsd.org In-Reply-To: <20050313171401.08B0D16A4DA@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050313171401.08B0D16A4DA@hub.freebsd.org> Subject: kern.maxpipekva exceeded, please see tuning(7) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John DeStefano List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2005 20:44:43 -0000 I have seen a mention or two of this error on the lists before, including this link to the "current" list I pulled up from Google: http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019150.html In my case, the errors began after my exploratory two-year-old found the shiny 'reset' button and could not resist its powers. I'm also getting HDD error messages on boot, 'fsck -y' shows all the file systems as read-only and returns errors on one of them, and I can no longer SSH into my system (due to, I assume, too many open file handles), or even get a command in on my console without an error popping in.. The solution does not seem clear cut to me, and it seems the error message itself does not provide valid (or, at least, sufficient) information. Could someone please help, or point me in the right direction? Thanks, as always, John