From owner-freebsd-hackers  Wed Oct 23 01:20:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA05011
          for hackers-outgoing; Wed, 23 Oct 1996 01:20:56 -0700 (PDT)
Received: from ns.pa-consulting.com (ns.pa-consulting.com [193.118.224.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA05002
          for <freebsd-hackers@freebsd.org>; Wed, 23 Oct 1996 01:20:51 -0700 (PDT)
Received: from SMTPGATE.PA-CONSULTING.COM by ns.pa-consulting.com (8.6.4) id JAA07593; Wed, 23 Oct 1996 09:31:17 +0100
Received: by SMTPGATE.PA-CONSULTING.COM with Microsoft Mail
	id <326E4992@SMTPGATE.PA-CONSULTING.COM>; Wed, 23 Oct 96 09:36:34 PDT
From: Duncan Barclay <Duncan.Barclay@pa-consulting.com>
To: freebsd-hackers <freebsd-hackers@freebsd.org>
Subject: Inode corruption on 2.1.5R
Date: Wed, 23 Oct 96 09:13:00 PDT
Message-ID: <326E4992@SMTPGATE.PA-CONSULTING.COM>
Encoding: 21 TEXT
X-Mailer: Microsoft Mail V3.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


A week or so ago I posted asking about inode
corruption under 2.1R when using the my floppy tape
drive. I have now upgraded to 2.1.5R and now
get inodes trashed when the floopy disk is accessed
using mtools.

I am being to suspect a hardware problem, possibly bus timings,
which is causing corruption of blocks being written to my (IDE) disks when
the floppy disk/tape is being accessed.

My system is
a  UMC based 486 board, with a SGS 486DX2-66, 20meg ram,
drives are both IDE hanging from a VESA IO card, also I have a NEC T130
8bit SCSI card, 3c509 standard VESA graphics. and fax modem, normal NEC
floppy controller with one 3.5floppy and a Connor TapeStor 800 tape drive
I running stock 2.1.5R.

Any ideas? I am getting a little too fimiliar with fsck...

Duncan Barclay