Date: Tue, 17 Mar 1998 16:41:39 +0000 (GMT) From: Paulo Cesar Pereira de Andrade <paulo@fiscodata-pr.netpar.com.br> To: "John S. Dyson" <dyson@FreeBSD.ORG> Cc: Karl Denninger <karl@mcs.net>, michaelh@cet.co.jp, current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected Message-ID: <Pine.BSF.3.96.980317160648.24088A-100000@fiscodata-pr.netpar.com.br> In-Reply-To: <199803170731.CAA11588@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Mar 1998, John S. Dyson wrote: > Karl Denninger said: > > > > Yes, and now I've done it twice more while trying to isolate this thing. > > > > The corruption comes back within minutes of starting a "make world". > > > Whomever is trying to work with late Sun, early Mon -current should > immediately stop, fsck their drives (if there is anything left), and > go back to a Sat kernel. If you are very aggressive, try the -current > as of now (as committed by me at around 01:00 EST on Tue.) I have cvsupped early saturday (about 02:00am Brazil), and while building world, received a error building gcc: <some-file>.o: malformed input file (not rel or archive) Looking the files, (one of them was /usr/obj/usr/src/gnu/usr.bin/cc/cc1plus/except.o) I saw it was fragments of c source code. This was after a crash while making world. Restarted a clean make world (/var/tmp as 8M MFS, and -j3) and it build with no errors. I got corrupted kernel .o files when compiling a library and the kernel at the same time. When compiling the kernel alone ld does not complain. The two times I thought it was operator error, because restarting did not repeat the problem. -- For perfect happiness, remember two things: (1) Be content with what you've got. (2) Be sure you've got plenty. 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.980317160648.24088A-100000>