From owner-freebsd-current Sun May 5 23:52:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 8C3BF37B406 for ; Sun, 5 May 2002 23:52:12 -0700 (PDT) Received: from localhost qhwt@smtp-send.myrealbox.com [61.198.248.149] by smtp-send.myrealbox.com with Novell NIMS $Revision: 2.88.1.1 $ on Novell NetWare; Mon, 06 May 2002 00:52:08 -0600 Date: Mon, 6 May 2002 15:53:27 +0900 From: qhwt@myrealbox.com To: Jeff Roberson Cc: current@freebsd.org Subject: Re: LOOKUP_SHARED is default now Message-ID: <20020506065327.GA34586.qhwt@myrealbox.com> Reply-To: current@freebsd.org References: <20020409010420.R16729-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020409010420.R16729-100000@mail.chesapeake.net> User-Agent: Mutt/1.5.0i X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. On Tue, Apr 09, 2002 at 01:08:04AM -0400, Jeff Roberson wrote: > This patch has seriously reduced file system deadlocks for several people. > It also makes concurrent file system access much faster in certain cases. > Since I have only heard good reports and no bad reports I'm going to > enable it by default. If you do experience some file system deadlocks > please let me know. You may revert to the previous behavior with 'options > LOOKUP_EXCLUSIVE'. I will take this away after a month or so if there are > no problems. I've been struggling upgrading kernel since beginning of April, and finally found I have to add "options LOOKUP_EXCLUSIVE" to my kernel config file. Without LOOKUP_EXCLUSIVE, - some of the processes stall in "inode" state, and can't be killed by any signals - shutting down(and maybe unmounting) the system results in the panic: lockmgr: upgrade exclusive lock The stalling processes are all touching files under nullfs-mounted directories, so I think nullfs code is not yet LOOKUP_SHARED-safe. If anyone is interested, I can post the backtrace and my kernel config (after upgrading the world and rebuilding the panicking kernel). Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message