Hi All,
We have a gtar file and we are trying to untar the file with the option
gtar -xvzf <filename>
The gtar gets us till the end and throws the error message as highlighed below
mfcp/XFHFCD2.CPY
mfcp/XFHFCD3.CPY
mfcp/XFHFCD.CPY
gzip: stdin: unexpected end of file
gtar:... (1 Reply)
I am trying to write a very large file, 570 gb, to a tape using gtar like this :
gtar czxf /dev/rmt/1 ./*
I get a message:
off_t value 570635451556 too large (max=68719476735)
It is writing to tape, but will it be good?
Thanks (1 Reply)
Hi all,
will gtar zcvf command work in csh and tcsh shells? Becuase when i'm executing one script in bash and ksh, it's working fine. But it's not working in csh and tcsh shells. We have to run multiple scripts in tcsh, so we can not change the shell while executing these scripts. One of my... (2 Replies)
Hello,
I'm experimenting a problem on my rh server.
Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux
It started with a segmentation fault on
#id root
To resolve it, I've installed
coreutils-4.5.3-28.4.i386.rpm
But, I... (6 Replies)
# service httpd start
Starting httpd: Syntax error on line 6 of /etc/httpd/conf.d/php.conf:
Cannot load /etc/httpd/modules/libphp4.so into server: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /lib/libgcc_s.so.1)
I... (2 Replies)
I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes.
When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error.
fatal: libdb2.so.1:... (2 Replies)
We are taking backup of our application data(cobol file system, AIX/unix) before and after EOD job runs. The data size is approximately 260 GB in biggest branch. To reduce the backup time, 5 parallel execution is scheduled through control-m which backups up the files in 5 different *.gz. The job... (2 Replies)
We are taking backup of our application data(cobol file system, AIX/unix) before and after EOD job runs. The data size is approximately 260 GB in biggest branch. To reduce the backup time, 5 parallel execution is scheduled through control-m which backups up the files in 5 different *.gz. The job... (8 Replies)
Hello,
I am trying to run a chess pairing program called Vega Chess on RHEL 6.5 Server
$ uname -a
Linux CDMA 2.6.32-431.el6.i686 #1 SMP Sun Nov 10 22:20:22 EST 2013 i686 i686 i386 GNU/Linux
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.5 (Santiago)This is the way I... (6 Replies)
Discussion started by: Ferocci
6 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)