From owner-freebsd-current Mon Mar 16 23:05:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17241 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:05:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17233; Mon, 16 Mar 1998 23:05:27 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id BAA00912; Tue, 17 Mar 1998 01:05:24 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id BAA05230; Tue, 17 Mar 1998 01:05:24 -0600 (CST) Message-ID: <19980317010523.23149@mcs.net> Date: Tue, 17 Mar 1998 01:05:23 -0600 From: Karl Denninger To: Daniel Berlin Cc: Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <19980317001100.18078@mcs.net> <19980317005403.27423@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980317005403.27423@mcs.net>; from Karl Denninger on Tue, Mar 17, 1998 at 12:54:03AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now I really don't get it. My "build" machine here has three drives on it. It has had three drives on it for a long, long time. The /usr/obj drive gets severely damaged during a "make world". The others do not. It is almost like /usr/obj is mounted async (but its not) and then the unmount is not sync'ing the disk before it dismounts it. Also, the drive is getting hosed DURING the build, because the cores that I'm getting are clearly due to damaged object files during the link process (I can rebuild the specific directory that faults, and it stops doing it). Also, I got a BUNCH of VM errors earlier this evening. I'm confused. I'm going to try to reproduce this some more - a kernel from last night (~2200), with CAM in it, doesn't produce the seg faults or the failures. That kernel has John Dyson's patches in it, but not the change to vfs_cluster.c which was committed today. Unfortunately, my attempt to back out the vfs_cluster.c change didn't do anything... so now I'm rather confused. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message