Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site aesat.UUCP
Path: utzoo!aesat!rwh
From: rwh@aesat.UUCP (Russell Herman)
Newsgroups: net.micro.cbm
Subject: Re: 1541 reliability update - (nf)
Message-ID: <181@aesat.UUCP>
Date: Wed, 18-Jul-84 09:31:44 EDT
Article-I.D.: aesat.181
Posted: Wed Jul 18 09:31:44 1984
Date-Received: Wed, 18-Jul-84 11:12:47 EDT
References: <1750@iddic.UUCP>, <36100087@uiucdcs.UUCP>
Organization: AES Data Inc., Mississauga Ont., Canada
Lines: 16

I always thought that scratching a file isn't SUPPOSED to update the BAM.
If it did, the trick of un-scratching accidently scratched files by setting
2**7 of byte zero of the directory entry wouldn't work after any further
file allocation, because some of those blocks might have been reused.

For those of you that don't realize what "validate" does, it searches
through all unscratched files on the disk, rebuilding the BAM from the
file chains. That's why you can't validate a disk with type relative
files on it: the side-sectors will be treated as unused.
-- 
  ______			Russ Herman
 /      \			{allegra,ihnp4,linus,decvax}!utzoo!aesat!rwh
@( ?  ? )@			
 (  ||  )			The opinions above are strictly personal, and 
 ( \__/ )			do not reflect those of my employer (or even
  \____/			possibly myself an hour from now.)