Date: Mon, 16 Nov 1998 15:43:00 -0800 (PST) From: Tom Bartol <bartol@salk.edu> To: Forrest Aldrich <forrie@forrie.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current Message-ID: <Pine.BSF.3.96.981116153210.342B-100000@eccles.salk.edu> In-Reply-To: <4.1.19981116174945.00a5fa00@206.25.93.69>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981116153210.342B-100000>