01-31-2007
If they are tar archives, you can almost surely read the tape on any other UNIX box that has a tape drive.
Even Windows winzip can read a tar file....
The only real problem is reading from the tape if you have no tape drives. There are data service bureaus that can read the tape to another format you can use.
.. assuming the data is in tar format.
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Gollum got crashed, needs Administrator's attention. Check this: https://www.unix.com/showthread.php?p=302093676 (0 Replies)
Discussion started by: tayyabq8
0 Replies
2. AIX
My AIX 5.3 Machine Carshed
Can any one tell some way to find out what went wrong..
I mean debug why it got creahed... (3 Replies)
Discussion started by: pbsrinivas
3 Replies
3. SuSE
Hi,
Running SLES 9 (update 4) on dell's poweredge 1950 server.
Kernel: 2.6.5-7.315-smp #1 SMP Wed Nov 26 13:03:18 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux
Yesterday night my monitoring service emailed me system(ssh/smtp) unreachable...I tried connection through ssh, it did not let me through... (0 Replies)
Discussion started by: upengan78
0 Replies
4. Linux
Hello,
Iam a running a apache webserver in CentOS and i get a heavy traffic about 2.5 lac pageviews daily and my db size is about 2GB. Now the problem is after serving some lacs of requests by apache....Both apache and mysql hangouts and the system gets hanged up...using all resources in the... (2 Replies)
Discussion started by: dheeraj4uuu
2 Replies
5. Solaris
My system is SUN Solaris 5.6 and one of the disks on the server got crashed. Here are the details
d23: Mirror
Submirror 0: d24
State: Okay
Submirror 1: d25
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
... (1 Reply)
Discussion started by: asalman.qazi
1 Replies
6. Linux
Hi everybody,
I want to find out all the processes that ran before a server crashed. Is that possible?
I've looked in /var/log/messages and found out that the system was out of memory.
A user probably wrote a script (in Perl or Python) that used up all available memory and crashed the... (11 Replies)
Discussion started by: z1dane
11 Replies
7. Red Hat
What do you check????
Thanks!
JC (0 Replies)
Discussion started by: 300zxmuro
0 Replies
8. Solaris
Hi Admins,
In my local Vmware system i have installed solaris but while getting my root disk mirrored in svm I changed the vfstab entries and rebooted the server , the server got crashed, and now the root file systems and other filesystems are crashed.
Please help me in recovering this. (2 Replies)
Discussion started by: Laxxi
2 Replies
9. IP Networking
If Freebsd DNS server that served 100 people is crashed. How to move this 100 people to a new FreeBSD DNS server as quickly as possible? (1 Reply)
Discussion started by: AIX_30
1 Replies
10. Solaris
Hi,
I have two Solaris 10 servers. First server crashed last week (Monday) and second one crashed over the weekend. I have checked the logs such as /var/adm/messages, syslog and dmesg. So for I found none. My management wants to know why the server crashed. I need to come with some kind of... (4 Replies)
Discussion started by: samnyc
4 Replies
TS(4) Kernel Interfaces Manual TS(4)
NAME
ts - TS-11 magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NTS ts_drives # TS11
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ts ? 172520 224 5 tsintr # ts11 driver
major device number(s):
raw: 8
block: 2
minor device encoding:
bits 0003 specify TS drive
bit 0004 specifies no-rewind operation
bit 0010 ignored
DESCRIPTION
The ts-11 combination provides a standard tape drive interface as described in mtio(4). The ts-11 operates only at 1600 bpi, and only one
transport is possible per controller.
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), ht(4), tm(4), dtab(5), autoconfig(8)
DIAGNOSTICS
ts%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.
ts%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.
ts%d: hard error bn%d xs0=%b xs1=%b xs2=%b xs3=%b. A hard error occurred on the tape at block bn; status registers 0-3 are printed in
octal and symbolically decoded as bits.
ts%d: addr mod 4 != 0. The address of a TS-11 command packet was not on an even longword boundary.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The device lives at the same address as a tm-11 tm(4).
3rd Berkeley Distribution January 28, 1988 TS(4)