Date: Tue, 29 Apr 1997 09:27:53 -0700 (PDT) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Brian Tao <taob@nbc.netcom.ca> Cc: freebsd-stable@freebsd.org Subject: Re: System freezes with 2.2-970420 Message-ID: <Pine.BSF.3.95.970429092154.6436C-100000@opus.cts.cwu.edu> In-Reply-To: <Pine.GSO.3.95.970428141010.12135M-100000@tor-adm1.nbc.netcom.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
I've seen the newfs'ing-the-block-device situation in recent RELENG_2_2 kernels and even 3.0-current. On the 2.2 machine I hit ^C - and at about that time everything hung. I didn't have physical access to the machine at the time so in desperation I ssh'd it a 'reboot' just in case. Nothing happened at first, and I then noticed that even ping requests of the machine were failing. But before the ssh command timed out the machine fully recovered... and then rebooted :( -Chris On Mon, 28 Apr 1997, Brian Tao wrote: > Changing from an old 3.0 snapshot to a recent 2.2-STABLE seems to > have fixed the ahc-related problems (it survived a 36-hour burn-in > with two 2940UW's and seven 4.3GB drives). However, I've come across > two ways to freeze up a 2.2-970420-RELENG system, one of them I was > able to reproduce consistently. > > The first is newfs'ing a disk via the block device rather than the > raw device. Doing so freezes up the machine at the same point in the > newfs each time. Using the raw device works fine: [...]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970429092154.6436C-100000>