home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!uwm.edu!spool.mu.edu!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!palantir.p.tvt.se!infolog!rabbe
- From: rabbe@infolog.se (Rabbe Fogelholm)
- Newsgroups: comp.sys.apollo
- Subject: Dealing with a badspot
- Message-ID: <1993Jan4.100208.10425@infolog.se>
- Date: 4 Jan 93 10:02:08 GMT
- Sender: rabbe@infolog.se (Rabbe Fogelholm)
- Organization: Infologics AB, Sollentuna, Sweden
- Lines: 29
-
- My Apollo disk currently contains a big file that I can't read
- properly. The read (2) routine fails with errno = 5 ("I/O error")
- after successfully reading several megabytes, but long before having
- reached end of file.
-
- Running SALVOL with the -A option produced the following diagnostic:
-
- I/O errors occurred in
- 50191 (32A-1-5) in VTOC
- returned status = 00080009
- >> name not found <<
- UID = 5D3A893B.300206EE VTOCX = 004FE850
-
- The UID above refers to the faulty file; I found out by using UCTOB
- and CTOB (surely there should be a more elegant way to find the UID of
- a file).
-
- Does this indicate a so-called badspot? Could I use INVOL option 9 to
- add it to the existing badspot list? If so, how do I derive the
- badspot address in the format required by INVOL? Do I at some point
- have to translate between base-10 and hexadecimal notation? (The
- pieces of information "50191" and "32A-1-5" above suggest a mixture of
- decimal and hex notation, and so does the listing produced by INVOL
- option 6 too.)
-
- Thankful for any advice. BTW, we run the fine old SR9.7.
-
- ________________________________________________________________________
- Rabbe Fogelholm, Infologics AB rabbe@infolog.se fax: +46 8 960846
-