Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uunet!mcsun!Germany.EU.net!bs From: bs@Germany.EU.net (Bernard Steiner) Newsgroups: comp.unix.bsd Subject: Re: Corrupted directory Date: 13 Oct 1992 10:13:22 GMT Organization: EUnet Backbone, Dortmund, Germany Lines: 17 Distribution: world Message-ID: <1be7g2INN9pi@Germany.EU.net> References: <24966.9210120127@thor.cf.ac.uk> <26947.9210120417@thor.cf.ac.uk> <1bd165INNrfe@iskut.ucs.ubc.ca> NNTP-Posting-Host: walhalla.germany.eu.net In article <26947.9210120417@thor.cf.ac.uk>, spedpr@thor.cf.ac.uk (Paul Richards) writes: =Using a program utilising unlink I managed to shift the awkward =directory to lost+found where it now resides as #04954. While this is =very nice it hasn't solved my problem of a corrupted filesystem. Oh =well, it seemed like a good thing to try. = =Is there a way to delete this inode. Fsck just isn't up to it. It goes =through the motions of fixing things but when I reboot the problem's =still there. go single user mode (hit ^C during boot cycle) clri <filesystem> <inode> fsck <filesystem> You may have to use the fixit disk, though. -Bernard