From owner-freebsd-current  Tue Nov 24 17:17:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA06526
          for freebsd-current-outgoing; Tue, 24 Nov 1998 17:17:27 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from root.com (root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06521
          for <current@FreeBSD.ORG>; Tue, 24 Nov 1998 17:17:25 -0800 (PST)
          (envelope-from root@root.com)
Received: from root.com (localhost [127.0.0.1])
	by root.com (8.8.8/8.8.5) with ESMTP id RAA25566;
	Tue, 24 Nov 1998 17:18:16 -0800 (PST)
Message-Id: <199811250118.RAA25566@root.com>
To: Greg Lehey <grog@lemis.com>
cc: "Roman V. Palagin" <romanp@wuppy.rcs.ru>,
        Karl Pielorz <kpielorz@tdx.co.uk>, current@FreeBSD.ORG
Subject: Re: Random craches under heavy(?) disk activity 
In-reply-to: Your message of "Wed, 25 Nov 1998 11:10:27 +1030."
             <19981125111027.G67961@freebie.lemis.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 24 Nov 1998 17:18:16 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>On Tuesday, 24 November 1998 at 12:54:35 +0300, Roman V. Palagin wrote:
>> On Tue, 24 Nov 1998, Karl Pielorz wrote:
>>
>>>
>>> I thought this had been fixed a while ago? - my system (current as of
>>> Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when
>>> busy (14 drives across 5 controllers) - it certainly makes it past the usual
>>> 2am cron-job's, and backups etc.
>>
>> It was fixed by McKusick 17/11/98. But it's very interesting:  I've
>> current as of 23/11/98 and kernel crashes without disabling 'realloc'
>> code, maximum uptime about 5-6 hours. Previous kernel was as of about
>> 20/11/98 and works without any problems 8-) It's looks like something
>> changed in src/sys tree.
>
>To be fair, Kirk wasn't 100% sure it would fix the problem.  He sent
>me a fix (I was the first to report the problem), and it hasn't
>occurred since.  It doesn't mean it's completely fixed, nor that your
>problem is the same.

   Guys, would you please look at the file sys/kern/vfs_cluster.c and verify
that you have rev 1.74?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message