From owner-freebsd-hackers Thu Oct 4 15:57:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by hub.freebsd.org (Postfix) with ESMTP id 882A137B401 for ; Thu, 4 Oct 2001 15:57:28 -0700 (PDT) Received: from office.tor.velocet.net (trooper.velocet.net [216.138.242.2]) by spitfire.velocet.net (Postfix) with ESMTP id 7C5CE44AAD9 for ; Thu, 4 Oct 2001 18:57:27 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.11.4/8.9.3) id f94MvRO35756; Thu, 4 Oct 2001 18:57:27 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15292.59734.934412.353194@trooper.velocet.net> Date: Thu, 4 Oct 2001 18:57:26 -0400 To: freebsd-hackers@freebsd.org Subject: NFS swap and locking X-Mailer: VM 6.92 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you've been following the situation, we have many diskless nodes that swap over NFS. We're using a patch (kindly provided to us) that allows swapon to specify a string to mount NFS swap after boot. I've been told (and it looks like) that it calls the same set of functions that the nfs swap option in the kernel would glean from DHCP, were we using that route. That's the background. Now, if I configure a swap-backed md disk (another patch we received) on the system and use it heavily with a particular application I get a locking panic from process id 4 (bufdaemon). panic: lockmgr pid 4 not exclusive lock holder unlocking 520 Any ideas? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message