From owner-freebsd-stable@FreeBSD.ORG Sun Aug 1 01:37:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 297651065676 for ; Sun, 1 Aug 2010 01:37:12 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id D8EFA8FC0A for ; Sun, 1 Aug 2010 01:37:11 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAKRsVEyDaFvO/2dsb2JhbACDE54FrHmQSYEmgyBzBIh/ X-IronPort-AV: E=Sophos;i="4.55,296,1278302400"; d="scan'208";a="89096686" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 31 Jul 2010 21:37:08 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id E558DB3F11; Sat, 31 Jul 2010 21:37:10 -0400 (EDT) Date: Sat, 31 Jul 2010 21:37:10 -0400 (EDT) From: Rick Macklem To: pluknet Message-ID: <1298502209.215859.1280626630797.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - FF3.0 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-stable Subject: Re: umount -f forces to panic 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: Sun, 01 Aug 2010 01:37:12 -0000 > From: "pluknet" > To: "freebsd-stable" > Sent: Friday, July 30, 2010 12:53:08 PM > Subject: umount -f forces to panic > Hi. > > This is 8.1 booted from NFS. > I did installworld to NFS on idle system, then it started > to print repeatedly "nfs server foo:mp lockd not responding". > umount returned EBUSY, umount -f dropped to panic: > I can't help w.r.t. fixing the lockd (NLM protocol). If you don't need locking to work across multiple clients for a given file, you can use the "nolockd" mount option. If you need locking on a given file to work across multiple clients, then you could consider trying NFSv4, which does have integrated file locking in the protocol. I am aware that "umount -f" crashes the system and hope to have a working "hard forced umount" implemented for 8.2. rick