From owner-freebsd-hackers  Tue Jun 13 13:28:51 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA08611
          for hackers-outgoing; Tue, 13 Jun 1995 13:28:51 -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 NAA08596
          for <hackers@freebsd.org>; Tue, 13 Jun 1995 13:28:47 -0700
Received: by iaehv.IAEhv.nl (8.6.12/1.63)
    id WAA02956; Tue, 13 Jun 1995 22:28:40 +0200
From: wjw@IAEhv.nl (Willem Jan Withagen)
Message-Id: <199506132028.WAA02956@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: Medium error
To: hackers@freebsd.org
Date: Tue, 13 Jun 1995 22:28:39 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 993       
Sender: hackers-owner@freebsd.org
Precedence: bulk

Hi,

A tricky question for the real serious hackers here:

We're running an ISP site and our newsdisk is giving us a hard time, but
it's real hard to replace the damn thing at the moment.

What do we have:
	A P90-asus with NCR controller with a quantum 2.1 Empire as sd2.

And this baby is generating a medium error on just one location. 
Jun 13 22:19:50 iaehv kernel: sd2(ncr0:2:0): medium error, info = 2817606 (decimal)

The funny (??) thing is that this cause I/O errors in INN in serveral spool
directories. Even after I created a real large file to try and cover the bad
spot with just-another-file.

So I'm starting to wonder: can the bad spot contain more than just one
directory which is getting trouble?

But the real serious question: Is there any way of getting this ONE error
out of the way by just any reasonable method?

We're are going to upgrade to a real large disk in near future, and
currently we'd like to transfer the 2 Gb of news just once?

Thanx,
	Willem Jan Withagen