From owner-freebsd-hackers  Thu Jun 15 00:28:37 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id AAA27979
          for hackers-outgoing; Thu, 15 Jun 1995 00:28:37 -0700
Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [192.87.208.2])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA27972
          for <hackers@freebsd.org>; Thu, 15 Jun 1995 00:28:31 -0700
Received: by iaehv.IAEhv.nl (8.6.12/1.63)
    id JAA07001; Thu, 15 Jun 1995 09:28:19 +0200
From: wjw@IAEhv.nl (Willem Jan Withagen)
Message-Id: <199506150728.JAA07001@iaehv.IAEhv.nl>
X-Disclaimer: iaehv.nl is a public access UNIX system and cannot be held
      	      responsible for the opinions of its individual users.
Subject: Crashed
To: admin@IAEhv.nl
Date: Thu, 15 Jun 1995 09:27:34 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 613       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

Hi,

Just another FAQ since I could go through the sources, and find out what
it is about.

This is on the system I described before, which had a medium error
on a Quantum 2.1G Empire (connected to a NCR controller, ASUS P90 with 2.0R)

What does it mean to get a:
	Jun 15 06:42:22 iaehv kernel: mb_map full
just befor a system crashes?
But no medium errors are detected around that same time.

Has it anything to do with the bad disk?

I think I found most of the places corrupted by the badspot and move these
dirs/files to places no longer used by the system. A sort of quarantine for
bad files.

Thanx,
	WjW