From owner-freebsd-current Mon Mar 16 21:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01241 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:56:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01235; Mon, 16 Mar 1998 21:56:32 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA08990; Tue, 17 Mar 1998 05:55:42 GMT Date: Tue, 17 Mar 1998 14:55:42 +0900 (JST) From: Michael Hancock To: Karl Denninger cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980316234921.07586@mcs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible that the previous kernel quietly trashed your disks and it didn't manifest itself until after the last vm fix commit? Regards, Mike Hancock On Mon, 16 Mar 1998, Karl Denninger wrote: > ************ URGENT ************** > > I strongly advise that you *DO NOT* use -CURRENT as it sits at the > present time. > > The kernel you build may do SEVERE damage to your filesystems. > > I am working on finding the commit which is causing this and will post to > the list as soon as I have identified it. > > This is not a trivial matter. It is a very good thing indeed that I use a > scratch disk for my /usr/obj area, or I would be really rather upset. :-) > > The symptoms are random core dumps and other problems - but the underlying > reason is that the filesystem has been trashed beyond belief! > > I unmounted the disk in question CLEANLY and found both partially truncated > and duplicate inodes all over it, along with severe internal file damage. > > I suspect the commit today in kern/vfs_cluster.c, as that's the only > filesystem or VM related commit that my first-level examination has found. > I am backing that out locally right now and will advise if it makes the > problem go away. > > Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > the problem. > > -- > -- > 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 > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message