| 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 |
Hi,
I'm having some problems with a customer who is trying to read some
files recorded by a Silicon Graphics system. It's a multivolume tar but he
never get a change volume request. He is running Digital UNIX v3.2c and
the tape used is a TLZ07.
The output of tar command:
# tar tv
blocksize = 20
drwxrwxr-x 213/15 0 Dec 6 17:45:54 1996 /sgs4/dsb8/divino
-rw-rw-rw- 213/15 598 Dec 3 18:38:57 1996 /sgs4/dsb8/divino/etopo5_s03.
ddr.a007F3
-rw-rw-rw- 213/15 598 Dec 4 18:34:09 1996 /sgs4/dsb8/divino/etopo5_s06.
ddr.a005gL
-rw-rw-rw- 213/15 598 Dec 3 19:17:36 1996 /sgs4/dsb8/divino/etopo5_s10.
ddr.a00691
-rw-rw-rw- 213/15 2635 Dec 3 14:14:20 1996 /sgs4/dsb8/divino/etopo5_s03.
his.a007F3
-rw-rw-rw- 213/15 2200 Dec 3 19:05:27 1996 /sgs4/dsb8/divino/etopo5_s06.
his.a005gL
-rw-rw-rw- 213/15 151 Dec 3 19:17:36 1996 /sgs4/dsb8/divino/etopo5_s10.
his.a00691
-rw-rw-r-- 213/15 683636 Dec 5 11:51:33 1996 /sgs4/dsb8/divino/etopo5_63_l
am.img.a003pM
-rw-rw-rw- 213/15 161141820 Dec 4 16:16:52 1996 /sgs4/dsb8/divino/s06_ozone
7.img.a0024z
tar: [offset 390m+270k+0]: I/O error
tar: [offset 390m+280k+0]: I/O error
tar: [offset 390m+290k+0]: I/O error
tar: [offset 390m+300k+0]: I/O error
. . . . .
. . . . .
. . . . .
tar: [offset 461m+676k+0]: I/O error
tar: [offset 461m+686k+0]: I/O error
tar: [offset 461m+696k+0]: I/O error
tar: [offset 461m+706k+0]: I/O error
tar: /sgs4/dsb8/divino/s06_ozone2.img.a001AM : File data is corrupt
Is it a midia problem or a multivolume tar compatibility problem ?
Thanks in advance,
Daniel Cardoso
MCS-CSC/Brazil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9396.1 | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Fri Apr 04 1997 20:33 | 4 | |
I'd use the error log formatter (uerf or dia) to see what those I/O errors are. Of course it could be that our tar and their tar don't agree on how to write a multi-volume archive and our tar is interpreting their method as a corrupt archive. | |||||