Date: Sun, 9 Apr 1995 19:27:39 -0700 (PDT) From: rmallory@wiley.csusb.edu (Rob Mallory) To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Arcive Viper QIC150 and tar Message-ID: <199504100227.AA18834@wiley.csusb.edu> In-Reply-To: <199504080843.KAA05362@uriah.heep.sax.de> from "J Wunsch" at Apr 8, 95 10:43:00 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > -why does it break tar? (tar czvf /dev/nrst0 /src/X11R6 segfaults..) > > I dunno if a segfault is an appropriate answer :), but at the very > least you deserve a data loss. You're attempting to write non-blocked > data (the output of gzip) to an unbuffered device. > > You can do one of the following: > > tar -cvzf - /foo /bar | dd obs=16k conv=osync of=/dev/nrst0 Now everything works fine. I had also used exactly that, and also with the --block-compress option for gtar, but it would still die. I had made world with -O3 , and everything "seemed" to work fine.(3/27/95) I just remade world with -O2, and now all the everything (nrst0.1 (thanks SM) work fine. I had suspected the -O3, and made tar with -O, just before rebuilding everything. no luck. It was either some O3 bogosity or something new in the libs since 3/27... Hmmmm. BTW, I never compile the kernel with anything except the default -O. Rob Mallory [rmallory@csusb.edu] Data Communications (909)880-7279 Cal State University San Bernardino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504100227.AA18834>