| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Whilst performing a vdump of an ADVFS domain a customer gets
no errors logged in either the errorlog or the log file of the
VDUMP.
In attempting a restore the customer gets an I/O error 5
reported and the errorlog shows the drive to have found
the tape to have a " MEDIA FORMAT CORRUPTED " error.
This does not happen on all tapes,I have asked the customer to do
the usual things regarding putting the offending tape to one-side,
cleaning the unit etc.
To compound things they have a TLZ07-VA connected to this
system and never have a problem vdumping or vrestoring.
IT'S rev is 553b
The customer is on DEC-UNIX V3.2G and dumping to a TLZ7L-VA
connected to a PMAZC-AA.
The firmware of the console is V6.7,the PMAZC-AA f/w is rev
V2.1 and the TLZ7L is at 4BQH.
Be grateful for any pointers
regards
tony melling
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9629.1 | DECWET::MARTIN | Mon Apr 28 1997 14:42 | 9 | ||
Hmm. You *might* be running into the problem where the original v3.2g vdump is incompatible with the original v3.2g vrestore. The on-tape format of vdump was changed in v4.0, and somehow that change got merged into a patch of vdump that made it into v3.2g. Of course vrestore wasn't touched, so it still only understands the v3.2 vdump format. There's a lot more discussion of this in DECWET::ADVFS_SUPPORT. --Ken | |||||
| 9629.2 | doesn't seem like version mismatch | DECWET::DADDAMIO | Design Twice, Code Once | Mon Apr 28 1997 16:17 | 7 |
I don't think the error referred to in .1 is happening. If that were
the problem you'd get a message saying that there was a version
mismatch between the vdump which created the tape and the vrestore
which is trying to read it and nothing else would happen. Unfortunately
I don't know what the problem really is, but since you are getting I/O
errors it does seem like it would be hardware, firmware, or media
problems.
| |||||