From mrami@mramirez.sy.yale.edu  Wed Apr 26 21:29:58 1995
Received: from mramirez.sy.yale.edu (mramirez.sy.yale.edu [130.132.57.207])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA15315
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 26 Apr 1995 21:29:55 -0700
Received: (from mrami@localhost) by mramirez.sy.yale.edu (8.6.9/8.6.9) id AAA06667; Thu, 27 Apr 1995 00:29:40 -0400
Message-Id: <199504270429.AAA06667@mramirez.sy.yale.edu>
Date: Thu, 27 Apr 1995 00:29:40 -0400
From: mrami@mramirez.sy.yale.edu
Reply-To: mrami@mramirez.sy.yale.edu
To: FreeBSD-gnats-submit@freebsd.org
Subject:
X-Send-Pr-Version: 3.2

>Number:         369
>Category:       i386
>Synopsis:       AHA-154X-A problems
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 26 21:30:01 1995
>Closed-Date:    Wed Feb 7 15:43:35 PST 1996
>Last-Modified:  Wed Feb  7 15:44:10 PST 1996
>Originator:     Marc Ramirez
>Release:        FreeBSD 2.0-950412-SNAP i386
>Organization:
You couldn't get a clue during the clue mating season in a field full of
horny clues if you smeared your body with clue musk and did the clue
mating dance. 
					- Edward Flaherty

>Environment:

	
??? 486DX/33 SiS Chipset, 20MB ram
Cardex Cobra ET4000/W32i video
Adaptec 1542A rev D -
	Conner CFA540S - target 0	512 meg
	Maxtor 7120SCS - target 1	120 meg
SMC Elite16 (I think; it's ed1, anyway)
??? floppy controller 2 drive, Colorado Jumbo 250
2 serial, parallel

>Description:

	 

I can read from my disks fine; however, writes seem to get corrupted.
Data as well as meta-data are affected by the problem.

>How-To-Repeat:

	
1) Downloaded boot floppies and bindist.

2) Install on drive 0; Reboot from sd0 and kernel panics right after
stating memory size. Reboot a couple of times; always get the same
panic.

3) Reinstall on drive 0; get a different panic.  Subsequent reboot
cause the new and improved panic.

4) Install 2.0R floppies (keeping SNAP bootblocks) and then install
the SNAP bindist (which is on sd1). On reboot, the kernel boots fine,
/etc/rc runs, I get a login prompt.

5) Run do_cksum.sh on SNAP bindist on sd1.  It runs with no errors.

6) Copy bindist from sd1 to sd0 and run do_cksum.sh on sd0 (copy)
bindist.  Half the files are corrupt. Re-run do_cksum.sh on the sd1
(original) bindist.  All is well.

7) Reinstall 2.0R on sd0.  An analysis of sd1 shows that the
filesystem has been corrupted. A file was rm'ed under the SNAP kernel.

>Fix:
	
	
I don't know.



>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: pst 
State-Changed-When: Wed Feb 7 15:43:35 PST 1996 
State-Changed-Why:  
Does not appear to be present in 2.1 or -current (at least no bug reports). 
>Unformatted:



950412-SNAP corrupts writes to disks
	support
