Date: Tue, 6 Jun 2000 17:00:17 -0400 From: Troy Arie Cobb <tcobb@staff.circle.net> To: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org> Subject: RE: FATAL FS Mount bug in -STABLE and -RELEASE Message-ID: <AE4A7B7EB10DD4118CBD0050DA196F4F0BE25F@FRIGGA>
next in thread | raw e-mail | index | archive | help
I'm a bit surprised that after two days no one has said anything about this fatal bug. Am I submitting this incorrectly? - Troy > -----Original Message----- > From: Troy Arie Cobb [mailto:tcobb@staff.circle.net] > Sent: Tuesday, June 06, 2000 7:35 AM > To: 'freebsd-stable@freebsd.org' > Subject: RE: FATAL FS Mount bug in -STABLE and -RELEASE > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE4A7B7EB10DD4118CBD0050DA196F4F0BE25F>