Well, I think I have to summarize
Thanx to John Seel, Dr. Blinn, John Venier and William Bochnik
The only recommendation that I got is to use the full path when
accessing the tape ( /dev/nrmt0h )
I still don't know why the tape drive is doing this, but I was able to
read the tape with the command
vrestore -i -f /dev/nrmt0h
but not with the command
vrestore -i (though it should )
One thing I noticed also that when trying to accessing the tape drive
(read or write operations) with the device name /dev/rmt0h, it doesn't
allow me and says *rmt0h is not a directory*
I have build the kernel, done the ./MAKEDEV command to create the
special files and ofcourse the doconfig and the rest of the kernel
rebuild procedure.
This is a strange behaviour. I think I am missing something
If IO got some answers or any progress I will summarize again.
MKMA
Original Message:
***************************************************************
Just to clear things up:
Yes, I used a no-rewind, but I did rewind it before I check it
using the restore, I have dump'd 6 save sets, I have even went to the
start of the 3rd set using command "mt fsf 2", but I still get the
same error, When I checked it on another system's tape drive, I checked
all of the 6 savesets and all are OK
MKMA
Hi all,
Machine is 2100, running Unix V 4.0G, attached to it a DLT Tape Drive.
I managed to install the SCSI Card and the tape drive, they work
fine except for one problem.
I was testing it, made a vdump for all our drives using command
#vdump -0 -u -f /dev/nrmt0h /mnt_points
works fine all the way, BUT
When I try to make a restore to check the backup using command
#vrestore -i (or even -t), It gives me the following error:
vrestore: unable to use save-set; invalid or corrupt format
************* PROGRAM ABORT **************
vrestore: can't obtain fileset attributes
I looked at the archives where one suggested a reboot for the
machine, which I did, but nothing happened and I got the same error
while reading.
I even make'd the device, built and reconfigured the kernel again,
but had the same error.
I think there is something happening while reading, so I can write
fine to the tape but get errors reading it.
FYI: I have checked the backup I made using another machine and
the backup is good, so it is not the tape.
Any Suggestions or remedies will be appreciated?
MKMA
******************************************************************
Received on Tue Aug 21 2001 - 12:57:25 NZST