Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!arclight.uoregon.edu!news-feed.inet.tele.dk!newsfeed.nacamar.de!news-kar1.dfn.de!news-stu1.dfn.de!news-mue1.dfn.de!news-nue1.dfn.de!news-lei1.dfn.de!news-ber1.dfn.de!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: fsck problem Date: 13 Mar 1997 23:48:43 GMT Organization: Private BSD site, Dresden Lines: 16 Message-ID: <5ga3or$pp@uriah.heep.sax.de> References: <E6wI6q.p0L@elcafe.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36992 busch@elcafe.com wrote: > Somehow my FreeBSD 2.1.5 machine managed to erase one directory's > ".." entry, rendering it not only unusable but also a source for > possible kernel panic's. fsck seem unable to deal with it, as it > asks to fix it, then does it (allegedly), and the same thing > will come up again at next boot time :-(( That means something is stomping on your disk. You gotta find it out. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)