From owner-freebsd-stable Thu May 13 14:37: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lazlo.internal.steam.com (lazlo.steam.com [199.108.84.37]) by hub.freebsd.org (Postfix) with ESMTP id BA6F114FD1 for ; Thu, 13 May 1999 14:36:58 -0700 (PDT) (envelope-from cliff@steam.com) Received: from lazlo.internal.steam.com (cliff@lazlo.internal.steam.com [192.168.32.2]) by lazlo.internal.steam.com (8.9.3/8.9.3) with ESMTP id OAA07655 for ; Thu, 13 May 1999 14:36:58 -0700 (PDT) Date: Thu, 13 May 1999 14:36:58 -0700 (PDT) From: Cliff Skolnick X-Sender: cliff@lazlo.internal.steam.com To: freebsd-stable@freebsd.org Subject: deadlock problem related to MFS & paging? In-Reply-To: <199905131502.IAA33482@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From an offlist email exchange with Cy, it seem that Cy and myself are both mounting /tmp with mount_mfs. We are also both locking up when the system is doing IO in general, paging, and lots of I/O to /tmp. I'm wondering if there is an interaction with the MFS code. I hope this is the case, and that removing the mount_mfs will stop the lockups. This would explain why more people are not having the same problem. Is anyone having these deadlocks not running MFS? I've emailed a couple other people that posted about deadlocks in the past few weeks to -stable asking them if they were running MFS. Cliff -- Cliff Skolnick | "They that can give up essential liberty to obtain Steam Tunnel Operations | a little temporary safety deserve neither liberty cliff@steam.com | nor safety." http://www.steam.com/ | -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message