Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!bogus.sura.net!jhunix.hcf.jhu.edu!jhunix.hcf.jhu.edu!not-for-mail
From: philippe@jhunix.hcf.jhu.edu (Philippe Pouliquen)
Newsgroups: comp.os.386bsd.bugs
Subject: Bug in 386bsd 0.2 (patches up to 110)
Date: 15 Mar 1993 17:36:00 -0500
Organization: Electrical and Computer Engineering, Johns Hopkins University, Baltimore, Md, USA
Lines: 38
Sender: philippe@zeus.ece.jhu.edu
Message-ID: <1o30cgINN87l@jhunix.hcf.jhu.edu>
NNTP-Posting-Host: jhunix.hcf.jhu.edu
Summary: Bug causes directory to disappear -- fsck finds it
I've upgraded recently with the patch84-110 from agate.berkeley, and
tested for this bug and it was still there. I haven't seen anyone
else report this (but I may have missed it) either. (Could also
be that no one is stupid enough to do this :-)
Using any shell, do the following:
mkdir junk
cd junk
touch file1 file2 file3 file4
cd ..
cat > junk.c
#include <stdio.h>
main()
{
printf("Hello world.\n");
}
^D
cc junk.c -o junk
At this point, on my system, the directory 'junk' disappears and is
replaced by the executable 'junk'. A reboot, and an fsck reattach the
directory 'junk' to the lost+found. Since this bug seems to affect the
integrity of the filesystem, I thought it was kind of important :-)
For those of you who are wondering how I discovered this bug: I was
cleaning up the source code for Analog (a circuit simulator from
Caltech), and I organized the source into three subdirectories ('ana',
'log', and 'psys'), and created a Makefile to generate 'log' and
'loged' in the parent directory (Note 'analog' and 'diglog' are hard
links to 'log'). Compiling erased the 'log', but I was suprised that
the disk didn't chatter too much (like it does when I rm -r a
directory with lots of files). So I rebooted and got my source back.
Philippe Pouliquen
philippe@zeus.ece.jhu.edu