From owner-freebsd-current Mon Aug 13 14:47: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 80AD537B401 for ; Mon, 13 Aug 2001 14:47:02 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7D7l1J01007 for current@freebsd.org; Mon, 13 Aug 2001 00:47:01 -0700 (PDT) (envelope-from obrien) Date: Mon, 13 Aug 2001 00:47:01 -0700 From: "David O'Brien" To: current@freebsd.org Subject: race-to-the-root, hello anyone out there? Message-ID: <20010813004701.A987@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 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 Hello?? Those that have committed to /sys in the past 1.5mo, awake? I am continuing to suffer thru what appears to be inode deadlocks where the resulting race-to-the-root soon locks everything up solid. Tried to figure out how to reproduce it on demand. All I can characterize is the file activity that FUBARs the system is in /tmp. What ideas do people have to solve the problem? crashdump are an impossibility due to the locked up disk system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message