From owner-freebsd-hackers  Sat Aug 16 01:25:27 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA13246
          for hackers-outgoing; Sat, 16 Aug 1997 01:25:27 -0700 (PDT)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13238
          for <hackers@freebsd.org>; Sat, 16 Aug 1997 01:25:22 -0700 (PDT)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
	by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id BAA07469
	for <hackers@freebsd.org>; Sat, 16 Aug 1997 01:25:21 -0700 (PDT)
Date: Sat, 16 Aug 1997 01:25:21 -0700 (PDT)
From: Jaye Mathisen  <mrcpu@cdsnet.net>
To: hackers@freebsd.org
Subject: Anudder DPT problem
Message-ID: <Pine.NEB.3.95.970816012323.4546C-100000@mail.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

P6200/2, 128MB RAM, DPT 3334 RAID controller, 5 Seagate Barracuda's, 2
disks in raid 1, 3 disks raid 5:

2.2.2-stable, with DPT 1.2 patch

I see the following after newfs'ing the raid 5:

ug 15 18:23:40 zzz /kernel: dpt0 ERROR: Marking 180582 (Prevent/Allow
Medium Removal [7.14]) on c0b0t1u0 
Aug 15 18:23:40 zzz /kernel: dpt0 ERROR: Marking 180582 (Prevent/Allow
Medium Removal [7.14]) on c0b0t1u0 
Aug 15 18:23:40 zzz /kernel:                    as late after 19693674usec
Aug 15 18:23:40 zzz /kernel:                    as late after 19693674usec
# Aug 15 18:23:43 zzz /kernel: dpt0: Salvaging Tx 180582 from the jaws of
destruction (5000/22415929)
Aug 15 18:23:43 zzz /kernel: dpt0: Salvaging Tx 180582 from the jaws of
destruction (5000/22415929)


Not exactly sure what it means.  The disk seems newfs'd OK, but don't like
the error message.