*BSD News Article 90906


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!howland.erols.net!blackbush.xlink.net!news.ppp.net!news.elcafe.net!busch
From: busch@elcafe.com
Subject: fsck problem
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
Lines: 16
Organization: Das elektronische Cafe
Message-ID: <E6wI6q.p0L@elcafe.com>
Date: Tue, 11 Mar 1997 22:52:01 GMT
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36945

Hi !

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 :-((

I know fsdb might be one tool to repair this, but a very dangerous
one, if one is not very familiar with the file system architecture.

Any suggestions (short of backup-newfs-restore cycle of course :-) 
are welcomed.

Rainer