First, my humblest apologies for asking this 'barely-scsi' related item on the
list, I'm really desperate for input on this. Scenario:
1) I do backups to a seagate 2/4G DAT using dump
2) I set the tape block size to 16384 using mt -f /dev/st0 setblk 16384
3) Three dump files are created, for /, /usr, and /home, respectively
4) Made huge system changes, like re-installing everything (system ran
everything from kernel 1.1.something to current 2.2.9.
5) Experienced 'brain-fart' and decided to dump /usr/src to tgz file on tape.
6) Stopped tape after overwriting my ONLY good backup 6M using 1024 block size
so there's the dilemma, I could care less about the first dump file /, and I
know it spanned 71785 blocks, (now these blocks counted as dump blocks of 1024
bytes, not tape blocks of 16384) To read the tape at all I have to setblk
1024, and I thought I could then set a file mark, mt -f /dev/nst0 setblk 16384,
and seek to the next file marker and I'd be set. But nooooooooooooo. I get
incorrect block size IO errors if I try to read at this point at either block
size.
I see two possible solutions, but have been unsuccessful in attaining the
proper results in my attempts. The first solution would be to find a way to
force read the entire tape into a file using dd, and then parsing that file
through whatever means deemed necessary. The Second is what I've been trying,
to calculate the exact position, and squash the IO errors as to force read at
that point using restore.
Any solutions, suggestions, guesses, hammers more than welcome! I really need
this data, there's 3 years of work on there!
Thanks in advance....
Russell
Words to Live by...
Work like you don't need money,
Love like you've never been hurt,
Dance like nobody's watching.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]