Xref: utzoo comp.unix.xenix:11350 comp.unix.wizards:21763 comp.unix.questions:21913 Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!ukc!reading!rosemary!ac1 From: ac1@rosemary.cs.reading.ac.uk (Andrew Cunningham) Newsgroups: comp.unix.xenix,comp.unix.wizards,comp.unix.questions Subject: Re: Corrupted Filesystem * IDEAS * Message-ID: <2327@onion.reading.ac.uk> Date: 2 May 90 13:54:41 GMT References: <1990Apr29.133610.11755@NCoast.ORG> Sender: news@reading.ac.uk Reply-To: ac1@rosemary.cs.reading.ac.uk (Andrew Cunningham) Organization: Comp. Sci. Dept., Reading Univ., UK. Lines: 22 In article peter@ficc.uu.net (Peter da Silva) writes: >I know the horses have already got out, but what we do at FICC is to >dd the superblock out of every file system every night, so if it *does* >get clobbered we can just dd it back and run fsck, which generally puts >everything back together. You could also try fsck -b. This number if the superblock location. I've yet to see a disk drive without a second superblock at 16 (/etc/fsck -b16) though yours may be different. Look in /etc/sbtab for a list if it's not your root partition that's gone with the wind...... AndyC Andrew Cunningham JANET:ac1@uk.ac.reading.cs.csug SNAIL: Dept. of Computer Science, Whiteknights, READING RG6 2AX FROM UselessCapitals IMPORT Disclaimer; "Sodomy non sapiens" (Buggered if I know) -Terry Pratchett "Mort"