Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!sitka.triumf.ca!felawka From: felawka@sitka.triumf.ca (Larry Felawka) Newsgroups: comp.unix.bsd Subject: Re: Corrupted directory Date: 12 Oct 1992 23:19:33 GMT Organization: TRIUMF, Vancouver BC Lines: 31 Distribution: world Message-ID: <1bd165INNrfe@iskut.ucs.ubc.ca> References: <24966.9210120127@thor.cf.ac.uk> <26947.9210120417@thor.cf.ac.uk> NNTP-Posting-Host: sitka.triumf.ca 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. |> -- |> Paul Richards at Cardiff university, UK. |> |> spedpr@uk.ac.cf.thor Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk |> UUCP: spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr |> +++ I am now in the process of installing 3386BSD, and what you are describing happens to me all the time! After the 2nd time it happened, I twigged that the "fixit.ds" floppy was aptly named. The procedure is to stop the endless cycle of fsck-ing and reboot-ing that the system undergoes (in my case), boot the fixit floppy (it contains a copy of fsck) and do a manual fsck of the hard drive (e.g. "fsck /dev/rwd0a"). The hard disk can then be rebooted with no difficulty. Good luck! -- Larry Felawka