From owner-freebsd-current Mon Mar 16 22:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05343 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:11:20 -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 WAA05289; Mon, 16 Mar 1998 22:11:09 -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 AAA29361; Tue, 17 Mar 1998 00:11:00 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id AAA04866; Tue, 17 Mar 1998 00:11:00 -0600 (CST) Message-ID: <19980317001100.18078@mcs.net> Date: Tue, 17 Mar 1998 00:11:00 -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: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Daniel Berlin on Tue, Mar 17, 1998 at 01:02:01AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Be VERY careful Dan. Unmount those disks and run a FSCK on them *right now*. The patch to vfs_cluster IS NOT the problem; I backed it out, and the kernel that I built after that still causes trouble. I'm still searching for the root cause of this. -- -- 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 On Tue, Mar 17, 1998 at 01:02:01AM -0500, Daniel Berlin wrote: > No no no, haven't you been watching those IBM commercials? > It was probably the malicious hackers who can break through routers > blocking their packets, cover their tracks and unleash viruses all over > your computer in a matter of seconds, unless you are using IBM certified > solutions. > I bet it was them. > Damn hax0rs. > > But seriously, i have just started to see a couple weird filesystem > related things since building a kernel a couple hours ago and rebooting a > couple times that weren't happening yesterday. > arghghghgh > --Dan > On Tue, 17 Mar 1998, Michael Hancock wrote: > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message