Well, look, it's clear you have variable block sizes, or a very small block size. Use the data from tcopy to use dd to save the contents of the records onto disk, like this:
Then run "file record*" to see file can determine what type of file each record is in. You might try:
to see if maybe the whole file together is a different thing.
At least now you have a template for getting all the records off the tape. Whether you can do anything with them or not is a different problem.
:confused:
Hello!!
I am a new UNIX user, and I need to back up some files, I have some old ones and I have been trying to delete the old information with 'mt erase' but I don't be sure if it works, and 'mt resert' but the it gave a message suggesting me to use 'scsiha -r' (but the last one... (1 Reply)
Hi,
I think this issue should be posted in a backup box, but there wasn't .
We have an issue that we made a backup on a DLT7000 tape using tar. Ones we check using : tar tvf /dev/rmt/0
It all works great on the same server.
Now ejecting the tape and putting it into server 2 with an SDLT... (0 Replies)
Hii alll
Thanks for the support, iam facing a problem regarding tanberg sdlt . iam trying to connect tanberg sdlt 160 to sun fire 880 r .As SUN FIRE DOSENT HAVE SCSI CONTROLLER IAM CONNECTING A ULTRA 2 SCSI CONTROLLER IN PCI SLOT AND FROM THERE IAM CONNECTING THE TANBERG SDLT 160.
MY FIRST... (1 Reply)
Greetings
I looking for the drivers for an sdlt tape drive for hp-ux 11.0. I think the drivers i need are stape and tape2 does anyone know where i can get them
Thanks
Alan (2 Replies)
I have a bunch of 4 mm DDS tapes that have two partitions. I read them on my HP-UX 10.20 box by referencing the device files /dev/rmt/0m (partition 0) and /dev/rmt/0mp (partition 1). Unfortunately, my HP-UX box was lightning struck last week so now I'm trying to read these tapes using Unix Services... (2 Replies)
Hi Community,
I've a V440 Sun Server with 2 device tape of 72GB. I have to backup a folder of 80 GB, so I have to use 2 tapes of 72GB (144 GB);
If I use vxdump command which are the options that I have to use?
When the first tape finishes does the system stop the backup?
Please help me... (1 Reply)
Hello, anybody out there that is using itdt to manage tape changes in a tape library. The help of itdt show a move subcommand but I can't get it to work.
Env:
AIX5.3
Dell PowerVault TL2000 tape library -> rmt1 Available 01-08-02 IBM 3580 Ultrium Tape Drive (FCP)
# itdt says it finds the... (3 Replies)
Discussion started by: petervg
3 Replies
LEARN ABOUT BSD
ht
HT(4) Kernel Interfaces Manual HT(4)NAME
ht - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)