From owner-freebsd-current Mon Mar 16 21:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29333 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:49: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 VAA29289; Mon, 16 Mar 1998 21:49:22 -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 XAA28510; Mon, 16 Mar 1998 23:49:21 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id XAA04580; Mon, 16 Mar 1998 23:49:21 -0600 (CST) Message-ID: <19980316234921.07586@mcs.net> Date: Mon, 16 Mar 1998 23:49:21 -0600 From: Karl Denninger To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ************ 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