Date: Tue, 7 May 2002 01:03:32 +1000 From: Joshua Goodall <joshua@roughtrade.net> To: current@freebsd.org Cc: Jeff Roberson <jroberson@chesapeake.net> Subject: Re: LOOKUP_SHARED is default now Message-ID: <20020506150332.GA38157@roughtrade.net> In-Reply-To: <20020506065327.GA34586.qhwt@myrealbox.com> References: <20020409010420.R16729-100000@mail.chesapeake.net> <20020506065327.GA34586.qhwt@myrealbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 06, 2002 at 03:53:27PM +0900, qhwt@myrealbox.com wrote: > 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). If you're feeling experimental try the change in PR kern/37270. It makes nullfs partially safe w.r.t. LOOKUP_SHARED, although there are still easily reproducable deadlocks (possible interactions with the syncer and/or vnlru processes but nothing concrete; at least, not from me). Joshua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020506150332.GA38157>