trohling@uceng.UC.EDU (tom rohling) (03/06/90)
Now that we are running 3.2, Has there been any major changes to
'tar' from a 3.1B release aside from things like the 'e' option
and the like that would cause the following kinda thing to happen?:
I had backed up alot of computations data on tape last spring and had
just used 'tar -cv data' which was the directory I had things in. Well
since 'data' took up more space than a single tape could hold, it
kindly asked to 'please insert a new tape and press enter' or some
congenial thing like that.
Anyway, now that I try to get the stuff back off it's not so kind
anymore and it doesn't recognize that the one tape ended and to
put in the next tape and continue reading.
The real problem is is that the end of the tape was in the middle
of one of the files that I need and hence it doesn't get it all off
the tape.
It wouldn't matter much if this wasn't an important data file but it
happens to be in the middle of some time series data that was quite
costly to generate on a X-MP and is a big part towards my impending
thesis deadline.
This never happened when I origionally did all this under 3.1B, at
that time it asked to put in the next tape and continue. We have not
changed the tape drive or anything since, only the OS.
Here's what transcribed this time:
[14] % tar -xveqqqqqq ** the more q's the better **
x data/cldm230.10, 1320000 bytes, 2579 blocks
x data/cldm230.20, 1760000 bytes, 3438 blocks
x data/cldm230.30, 1760000 bytes, 3438 blocks
x data/cldm230.40, 1760000 bytes, 3438 blocks
.... a whole bunch of filenames deleted for brevity
x data/cldm25.40, 880000 bytes, 1719 blocks
x data/cldm25.50, 880000 bytes, 1719 blocks
x data/cldm25.60, 880000 bytes, 1719 blocksmyio(read): wanted 204800 bytes, got
0
tar: tape premature EOF
[15] % ls
So here's where I put in the next tape that it was supposed to ask me
to put in and then try to continue the process. The next error isn't
suprising though,
[16] % tar -xveqqqqqqq ** without the e it wouldn't even start reading **
tar: Directory checksum error. Continuing...................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
.............................................................................
...........................................................................OK
x data/cldm25.70, 880000 bytes, 1719 blocks
x data/cldm25.80, 880000 bytes, 1719 blocks
x data/cldm25.90, 880000 bytes, 1719 blocks
..... and on it continues.
If it helps here's what I get when I list the inventory:
[20] % hinv
12 MHZ IP4 Processor
FPU: MIPS R2010A/R3010 VLSI Floating Point Chip Revision: 1.5
CPU: MIPS R2000A/R3000 Processor Chip Revision: 1.6
Data cache size: 32 Kbytes
Instruction cache size: 64 Kbytes
Main memory size: 16 Mbytes
Interphase 3201 2-drive ESDI disk controller 0
ESDI Disk drive: unit 0 on Interphase controller 0
CMC ENP-10 Ethernet controller 0, firmware version 0 (CMC)
Integral SCSI controller WD33C93
Tape drive: unit 7 on SCSI controller 0: QIC 24
[21] %
H H EEEE L PPPP !!
H H E L P P !!
HHHHH EEE L PPPP !!
H H E L P !!
H H EEEE LLLL P ..
Any whizz's know what I could do to get this back?
HEAPS OF THANKS IN ADVANCE
******************************************************************************
TOM ROHLING
trohling@uceng.uc.edu
or
rohling@afiris.ase.uc.edu
******************************************************************************wood@acf4.NYU.EDU (David Wood) (03/08/90)
Could it be that when you originally made the tar tape the tar you were using was gnu tar. I know that their makefile uses the name 'tar' when installing the binary. If that tar got lost and overwritten with the original during the upgrade this might explain your problems. Although, even gnu tar requires the -M option for multi- volumes.