home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!swrinde!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!crdgw1!newsun!donp
- From: donp@novell.com (don provan)
- Newsgroups: comp.sys.novell
- Subject: Re: VREPAIR, errors.. clues?
- Message-ID: <1993Jan3.085306.8153@novell.com>
- Date: 3 Jan 93 08:53:06 GMT
- References: <1992Dec23.215332.1@tango.cchs.su.oz.au> <1992Dec28.175239.5756@novell.com>
- Sender: news@novell.com (The Netnews Manager)
- Organization: Novell, Inc., San Jose, California
- Lines: 23
- Nntp-Posting-Host: na.sjf.novell.com
-
- In article <1992Dec28.175239.5756@novell.com> dseeman@novell.com (Daniel Seeman) writes:
- >Don P., do you understand why this is ("...be sure to run VREPAIR
- >until you find zero errors, then run it once more to verify there were
- >no errors left...")?
-
- I don't have any specific knowledge about why this is necessary with
- NetWare and VRepair, but from past experience with similar facilities
- in various operating systems, there are typically two causes for
- damage repair to require multiple passes. One is that some damage is
- masked by other damage. The first pass fixing the obscuring damage
- reveals hidden damage. The other is that some damage repair can
- move damage from one class to another. For example, deleting a bad
- directory entry in one pass might mean that disk blocks hanging from
- that directory entry would show up as "lost" blocks in a subsequent
- pass. (Shows what i know about VRepair: i had to fall back on an
- example from TOPS-10 because i don't know enough about what kinds of
- damage VRepair fixes nor what it calls them.)
-
- Hope this helps. Someone that has more experience with VRepair might
- want to compare my theory with what VRepair actually does to see if
- what i've said is relevant.
- don provan
- donp@novell.com
-