From owner-freebsd-hackers Wed Mar 29 09:32:00 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA22507 for hackers-outgoing; Wed, 29 Mar 1995 09:32:00 -0800 Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA22501 for ; Wed, 29 Mar 1995 09:31:59 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by wcarchive.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA11670 for ; Wed, 29 Mar 1995 09:31:08 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id KAA15329; Wed, 29 Mar 1995 10:31:29 -0700 Date: Wed, 29 Mar 1995 10:31:29 -0700 From: Nate Williams Message-Id: <199503291731.KAA15329@trout.sri.MT.net> In-Reply-To: william pechter ILEX "1.1.5.1 memory problem" (Mar 29, 12:07pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: william pechter ILEX , FreeBSD-hackers@wcarchive.cdrom.com (FreeBSD-hackers) Subject: Re: 1.1.5.1 memory problem Sender: hackers-owner@FreeBSD.org Precedence: bulk > I picked up this failure under 1.1.5.1's daily script... > > Rotating messages: > mv: rename messages.1 to messages.2: No such file or directory > > Rebuilding locate database: > free(a) above top of memory.memtop = 3e400 membot = 382f0. > free(3b708) bad block.memtop = 3e400 membot = 382f0. > free(3b718) bad block.memtop = 3e400 membot = 382f0. > > Anyone have an idea where to look for this problem. I saw something similar to this on a machine whose disk was going bad, but occasionally worked. Sometimes it could read the data, and other times it couldn't. We replaced the drive and all was well. (I'm not sure if the bad spot was on the FS or the swap partition) Nate