Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!snorkelwacker.mit.edu!stanford.edu!neon.Stanford.EDU!torrie From: torrie@cs.stanford.edu (Evan Torrie) Newsgroups: comp.sys.mac.system Subject: Re: System 7 re-verify Message-ID: <1991Apr10.235034.7512@neon.Stanford.EDU> Date: 10 Apr 91 23:50:34 GMT References: <1991Apr10.221317.10619@mintaka.lcs.mit.edu> Sender: torrie@neon.Stanford.EDU (Evan James Torrie) Organization: Computer Science Department, Stanford University, Ca , USA Lines: 26 rsfinn@CONCERTO.LCS.MIT.EDU (Russell S. Finn) writes: >In article , jp48+@andrew.cmu.edu (Jonathan Pace) writes: >|> >|> I just erased a disk that was giving me problems and I watched the usually >|> boring description of what was happening. Thing is, system 7 (b4) said it >|> was re-verifying the disk at one point. It took about as much time as the >|> normal verify, which it also did. >|> >|> Is this a feature that it does all the time, or is it just used on disks >|> that are giving screwy verification results? >Congratulations, you've just discovered the new "block-sparing" feature >of System 7, described in one of the most recent batch of Tech Notes. This is documented in TN #287: Hey Buddy, Can You Spare A Block? Essentially, it rescans the disk after a verification failure, reading and writing a track at a time to find which one has an error. It removes these sectors from the volume bitmap of available storage. -- ------------------------------------------------------------------------------ Evan Torrie. Stanford University, Class of 199? torrie@cs.stanford.edu Fame, fame, fame... What's it good for? Ab-so-lute-ly nothing