From owner-freebsd-stable Tue Jun 6 4:36: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frigga.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 00E1D37C00B for ; Tue, 6 Jun 2000 04:35:48 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FRIGGA with Internet Mail Service (5.5.2650.21) id ; Tue, 6 Jun 2000 07:35:32 -0400 Message-ID: From: Troy Arie Cobb To: "'freebsd-stable@freebsd.org'" Subject: RE: FATAL FS Mount bug in -STABLE and -RELEASE Date: Tue, 6 Jun 2000 07:35:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More information: this problem does NOT occur on the latest 3.4-STABLE release. > -----Original Message----- > From: Troy Arie Cobb [mailto:tcobb@staff.circle.net] > Sent: Monday, June 05, 2000 1:10 PM > > I've found a fatal filesystem mount bug in both 4.0-STABLE > and 4.0-RELEASE, > tested on the 20000604 snapshot of 4.0. > > With both the GENERIC kernel and a custom kernel, the system hangs > tight when more than about 256 filesystems are mounted. I've > tested this with loopback NFS mounts, remote NFS mounts, > and local NULL mounts. The machine freezes, responds to pings and > changing of virtual console, but accepts no input. No > errors are written to > /var/log or console. A hard reset is the only way out, CTRL-ALT-DEL > doesn't work. > > Please tell me what other info we can provide. This should > be easy to > reproduce, though I'd be happy to give anyone the perl > scripts we use > to tickle the bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message