Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!tank.news.pipex.net!pipex!dish.news.pipex.net!pipex!news.be.innet.net!INbe.net!news.nl.innet.net!INnl.net!hunter.premier.net!news.uoregon.edu!arclight.uoregon.edu!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: BAD SUPER BLOCK hang... how hosed am I? Date: 3 Jul 1996 00:45:38 -0500 Organization: Coverform Ltd. Lines: 40 Message-ID: <4rd1e2$j9@anorak.coverform.lan> References: <31D872EC.41C6@ucdavis.edu> NNTP-Posting-Host: localhost.coverform.lan X-NNTP-Posting-Host: awfulhak.demon.co.uk X-Newsreader: TIN [version 1.2 PL2] Michael White (mdwhite@ucdavis.edu) wrote: : The error that I saw was in listing some of the ports stuff. The : listing looks like: : /u/ports/audio: : total 1701209510 : -rw-r--r-- 1 root 523 411 Apr 12 02:13 Makefile : drwxr-xr-x 5 root 523 512 May 15 19:58 gmod/ : b--xr-Sr-t 26213 1701209446 1711957350 101, 1701183590 Jun 9 01:23 gsm* : drwxrwxr-x 5 root 523 512 Apr 11 1995 maplay/ : .... : There are a number of files like this. I cannot delete them. Now : if I loose this stuff it is no big deal, but I am wondering what : caused the problem & how to fix it. Could I have something set up : wrong (i.e. could this have something to do with the >500 Mb on : the disk)? I've had this before - after hosed superblock problems. You're "gsm" file is already *gone*. To remove these nasty files, go to single user mode, to a "ls -i" to get the inode number, sync, clear the inode and "halt". Inodes are cleared with say "clri /dev/rsd0a 1234" to clear inode 1234 from your first partition of your first SCSI slice. It's important that you sync before and halt afterwards - otherwise a dirty disk buffer will overwrite your "clri" modifications - updating the inode again. After you've done all this, you'll need to fsck - even if the FS says it's clean. Boot with -s and run fsck [-y] manually. I've been lucky enough that this has only happened to important files once (although that was /usr/lib/*). I normally see this sort of thing in the lost+found directory. -- Brian <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....