From owner-freebsd-bugs  Wed Apr 26 21:30:02 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id VAA15342
          for bugs-outgoing; Wed, 26 Apr 1995 21:30:02 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id VAA15335
          ; Wed, 26 Apr 1995 21:30:01 -0700
Date: Wed, 26 Apr 1995 21:30:01 -0700
Message-Id: <199504270430.VAA15335@freefall.cdrom.com>
From: mrami@mramirez.sy.yale.edu
Reply-To: mrami@mramirez.sy.yale.edu
To: freebsd-bugs
Subject: i386/369: 
In-Reply-To: Your message of Thu, 27 Apr 1995 00:29:40 -0400
	<199504270429.AAA06667@mramirez.sy.yale.edu>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         369
>Category:       i386
>Synopsis:       
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 26 21:30:01 1995
>Originator:     Marc Ramirez
>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

>Release:        FreeBSD 2.0-950412-SNAP i386
>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.



>Audit-Trail:
>Unformatted:


950412-SNAP corrupts writes to disks
	support