Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!ucsd!sdcc6!beowulf!jlodman
From: jlodman@beowulf.ucsd.edu (Michael Lodman)
Newsgroups: comp.unix.sysv386
Subject: boot floppy
Message-ID: <18792@sdcc6.ucsd.edu>
Date: 29 Apr 91 16:50:07 GMT
Sender: news@sdcc6.ucsd.edu
Organization: CSE Department, UC San Diego
Lines: 20

I have tried making a file system on /dev/dsk/f0q15d (no boot track)
and have gotten the thing created after some pain. When I mount
the filesystem, there are no errors.

If I then umount it and remount it, the filesystem has gone really
crazy, with allocations that now make no sense, and that fsck can't repair.
It is almost as if the filesystem is slowly deteriorating. 
Eventually, fsck deletes the root inode and the filesystem is gone.
It almost seems as if umount is destroying it.

Anybody have any guesses as to what went wrong? I hope to be using
ISC Unix again soon but would like to get this problem resolved.
The particulars were a 386 clone at 25MHz, and ISC 2.02.
It didn't seem to be limited to a particular high density floppy.
I needed to keep the boot track clear, so I didn't use /dev/dsk/f0q15dt.

-- 
Michael Lodman	Department of Computer Science Engineering
	University of California, San Diego
jlodman@cs.ucsd.edu			(619) 672-1673