Bad block forwarding

Article View: mod.computers.apollo

Article #307

Back to mod.computers.apollo Previous Next

#307

From: peterson
Date: Mon, 05 Jan 1987 17:07

13 lines
1055 bytes

Does anybody know how to go about adding bad blocks to an Aegis filesystem
that's in use?  I tried the following procedure:

	Use /systest/ssr_util/lsyserr to print out the disk errors

	Take the hexadecimal "daddr" value from lsyserr's listing and
	add it to the badspot list using invol (option 9)

	Run salvol to set the trouble flag in any affected files.

What I'm not sure about is if the numbers reported by lsyserr are the same
ones used by invol.  Has anybody seem a documented procedure for doing this
operation?

Technical Details

Message-ID: <8701051707.AA01631@utah-cs.ARPA>

Path: arc1-ca.pugleaf.net!utzoo!decvax!ucbvax!UTAH-CS.ARPA!peterson

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!decvax!ucbvax!UTAH-CS.ARPA!peterson
From: peterson@UTAH-CS.ARPA.UUCP
Newsgroups: mod.computers.apollo
Subject: Bad block forwarding
Message-ID: <8701051707.AA01631@utah-cs.ARPA>
Date: Mon, 5-Jan-87 12:07:28 EST
Article-I.D.: utah-cs.8701051707.AA01631
Posted: Mon Jan  5 12:07:28 1987
Date-Received: Mon, 5-Jan-87 19:22:51 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: apollo@yale-comix.arpa