From owner-freebsd-current Mon Nov 16 15:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06358 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:42:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06275 for ; Mon, 16 Nov 1998 15:42:20 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id PAA00512; Mon, 16 Nov 1998 15:41:45 -0800 (PST) Date: Mon, 16 Nov 1998 15:43:00 -0800 (PST) From: Tom Bartol To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <4.1.19981116174945.00a5fa00@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Forrest Aldrich wrote: [snip] > I am beginning to suspect a filesystem bug. When this happens, something > doesn't > get handled correctly with the standard fsck. I end up having to bring my > machine > into single-user mode to perform the fsck manually. > > Anyone else? > I'm getting the crashes but fsck is able to repair my system just fine. I haven't been able to get a dump. The crashes occur during heavy local file I/O (such as a buildworld or cvsup of ports-all). This is on a system current as of 8:OOAM PST this morning. 400MHz PII SMP 512MB RAM, / and /usr on SEAGATE ST34502LW with adaptec 7890, /usr/scratch is RAID 0 on two IBM 9ZX's with DPT PM3334UW FW Rev. 07M0, 2 channels. I'm running a current kernel from Oct 29 at the moment as a work-around -- Trying to buildworld cvsupped moments ago to see if the problem has in fact been fixed as has been mentioned. If not, I'll get more hard-nosed about capturing a useful dump... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message