From owner-freebsd-stable@FreeBSD.ORG Sat Jun 10 22:23:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 2D2B716A41B for ; Sat, 10 Jun 2006 22:23:48 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D0D43D48 for ; Sat, 10 Jun 2006 22:23:47 +0000 (GMT) (envelope-from zbeeble@gmail.com) Received: by ug-out-1314.google.com with SMTP id j40so1739509ugd for ; Sat, 10 Jun 2006 15:23:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=W3g5ZfMWR+NyPtlnMsuPU4Qru9uEEmKs65D4scbBAuVnZW43uzzc++2qy/opKzl9tSHBOGAS94DKTdrt46L39CbrH+Tt3Wxc6IKZ1DrUVzozKg22FToOemvnnedb7p/NTO2Y0yCNwowVvR6+0fhonELdWF4H4A1yNQ0PqZH1ZQo= Received: by 10.67.100.12 with SMTP id c12mr3750780ugm; Sat, 10 Jun 2006 15:23:46 -0700 (PDT) Received: by 10.67.96.5 with HTTP; Sat, 10 Jun 2006 15:23:46 -0700 (PDT) Message-ID: <5f67a8c40606101523q42311e46y51d23786ef3a15c0@mail.gmail.com> Date: Sat, 10 Jun 2006 18:23:46 -0400 From: "Zaphod Beeblebrox" To: "Mark Morley" In-Reply-To: <448b246d-9da2@helpdesk.islandnet.com> MIME-Version: 1.0 References: <447fa140-96fe@helpdesk.islandnet.com> <448b246d-9da2@helpdesk.islandnet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: NFS processes locking up!! 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: Sat, 10 Jun 2006 22:23:48 -0000 [nfsd's and other processes locking in 'D' state] One thing I've seen cause this kind of thing is a disk that needs to be manually fsck'd. Try bringing up the system in single user and manually fsck'ing the volume. I have no idea what causes this kind of state --- where the disk is bad, but not calling for an fsck. It could just be random bad bits, but I've seen this behaviour more than once.