Sponsored Content
Full Discussion: cp from tspe a file...
Special Forums Hardware Filesystems, Disks and Memory cp from tspe a file... Post 17405 by spyros on Thursday 14th of March 2002 03:27:45 PM
Old 03-14-2002
Question

Well, i don't really know what the exact error message because I don't have the tape right now to try it, but when I get the tape I'll have to copy it emidiatelly so I have to know...can you please help me????

thanx!!Smilie
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Match list of strings in File A and compare with File B, C and write to a output file in CSV format

Hi Friends, I'm a great fan of this forum... it has helped me tone my skills in shell scripting. I have a challenge here, which I'm sure you guys would help me in achieving... File A has a list of job ids and I need to compare this with the File B (*.log) and File C (extend *.log) and copy... (6 Replies)
Discussion started by: asnandhakumar
6 Replies

2. Shell Programming and Scripting

Compare 2 text file with 1 column in each file and write mismatch data to 3rd file

Hi, I need to compare 2 text files with around 60000 rows and 1 column. I need to compare these and write the mismatch data to 3rd file. File1 - file2 = file3 wc -l file1.txt 58112 wc -l file2.txt 55260 head -5 file1.txt 101214200123 101214700300 101250030067 101214100500... (10 Replies)
Discussion started by: Divya Nochiyil
10 Replies

3. Shell Programming and Scripting

Shell script (sh file) logic to compare contents of one file with another file and output to file

Shell script logic Hi I have 2 input files like with file 1 content as (file1) "BRGTEST-242" a.txt "BRGTEST-240" a.txt "BRGTEST-219" e.txt File 2 contents as fle(2) "BRGTEST-244" a.txt "BRGTEST-244" b.txt "BRGTEST-231" c.txt "BRGTEST-231" d.txt "BRGTEST-221" e.txt I want to get... (22 Replies)
Discussion started by: pottic
22 Replies
TM(4)							     Kernel Interfaces Manual							     TM(4)

NAME
tm - TM-11/TE-10 magtape interface SYNOPSIS
/sys/conf/SYSTEM: # Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250 # controller. For more details, see /sys/pdpuba/tm.c. NTM tm_drives # TM11 AVIVTM YES # AVIV 800/1600/6250 controller /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments tm ? 172520 224 5 tmintr # tm11 driver major device number(s): raw: 7 block: 1 minor device encoding: bits 0003 specify TS drive bit 0004 specifies no-rewind operation bits 0030 specify recording density: 0000: 800BPI 0010: 1600BPI (AVIVTM and some other controllers) 0020: 6250BPI (AVIVTM only) DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive interface as described in mtio(4). The standard DEC tm-11 operates only at 800 bpi. Other controllers of this type may also allow operation at 1600 bpi, under software control or by switching manually. 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), ts(4), mt(4), dtab(5), autoconfig(8) DIAGNOSTICS
te%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. te%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. te%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. te%d: hard error bn%d er=%b. A tape error occurred at block bn; the tm error register is 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. te%d: lost interrupt. A tape operation did not complete within a reasonable time, most likely because the tape was taken off-line during rewind or lost vacuum. The controller should, but does not, give an interrupt in these cases. The device will be made available again after this message, but any current open reference to the device will return an error as the operation in progress aborts. BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed. 3rd Berkeley Distribution January 28, 1988 TM(4)
All times are GMT -4. The time now is 03:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy