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
tm
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)