>Number:         1815
>Category:       kern
>Synopsis:       Filesystem destroys itself
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec  5 21:20:01 1995
>Last-Modified:
>Originator:     Andrew Cassin
>Organization:
None
>Release:        1.1
>Environment:
NetBSD 1.1, on Intel 486DX2/66 with 2 ide drives
System: NetBSD knopfler 1.1 NetBSD 1.1 (knopfler) #0: Tue Dec 5 03:52:01 PST 1995 root@knopfler:/usr/src/sys/arch/i386/compile/knopfler i386


>Description:

I have recently installed 1.1 (previously using 1.0 although I newfs'ed 
the system partition to avoid old gunk hanging around) and it appears to
trash filesystems after some usage. I have no idea why but here is some
ls output which may be of use:

4324 brwSr-----  1 1536  2428750080    0, 199 Jan  7  1970 /dev/ttyp5
total 220
br-xr-xr-x  29283 1696625253  1701143416   32,  97 Nov 16 07:51 Globals.html
-r-s-w-r-x  22245 76382212    263769221              3127761439104700346 Jul 21  1970 Windows.html

In one example, I created a non-existant file via touch, and an 
immediate 'ls -l' showed its file size to be in the gigabyte range. So far,
I have had this problem 3 times on the root filesystem, and once on the 
/local filesytem. (Windows.html and Globals.html are from the 
tcl 7.4 & tk 4.0).

I have rebuilt/reinstalled all binaries in /sbin (fearing corruption of
fsck on the install floppy) but cksums show no difference. 

Here is some system details from df and dmesg:

Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/wd0a      295070   156930   123386    56%    /
/dev/wd1a      554940   180226   346966    34%    /home
/dev/wd1e      458798   211046   224812    48%    /local
procfs              4        4        0   100%    /proc
kernfs              1        1        0   100%    /kern

NetBSD 1.1 (knopfler) #0: Tue Dec  5 03:52:01 PST 1995
    root@knopfler:/usr/src/sys/arch/i386/compile/knopfler
CPU: i486DX (486-class CPU)
real mem  = 16384000
avail mem = 14290944
using 225 buffers containing 921600 bytes of memory
isa0 (root)
com0 at isa0 port 0x3f8-0x3ff irq 4: ns8250 or ns16450, no fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns8250 or ns16450, no fifo
lpt0 at isa0 port 0x378-0x37f irq 7
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
wd0 at wdc0 drive 0: 329MB, 790 cyl, 15 head, 57 sec, 512 bytes/sec <Maxtor 7345 AT>
wd0: using 16-sector 16-bit pio transfers, chs addressing
wd1 at wdc0 drive 1: 1039MB, 2112 cyl, 16 head, 63 sec, 512 bytes/sec <QUANTUM FIREBALL1080A>
wd1: using 8-sector 16-bit pio transfers, lba addressing
npx0 at isa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.2MB 80 cyl, 2 head, 15 sec
fd1 at fdc0 drive 1: 1.44MB 80 cyl, 2 head, 18 sec
root device eisa not configured
root device pci not configured
biomask 4040 netmask 0 ttymask 1a

>How-To-Repeat:
	unknown, its difficult to tell whether fsck is creating the problem 
	or whether it is normal user-land activity.
>Fix:
	unknown
>Audit-Trail:
>Unformatted: