Hi Managers,
I got only one response from Jim Belonis who wrote :
This is typically an error message caused by attempting to dump from an
Digital Unix computer to some other brand which uses a different 'rmt'
program (which is used by rdump).
It can also be caused by a bad 'dot' file such as a .cshrc
which outputs some unexpected characters when it is run on the
tape-drive machine for the 'rmt' process.
You should do rsh <tape-machine> date and verify that ONLY the date is
displayed.
I suggest you avoid rdump because it is 2-4 times slower than a 'dump
pipe' something like
dump <arguments> - /partition | rsh tape-machine dd bs=blocksize
of=<tapedev>
It also avoids such incompatibilities (Digital Unix is the only REAL
offender that I know of. Several of its rmt internal commands (see 'man
rmt') conflict with commonly used commands on other architectures' rmt
such as Sun and SGI. Digital Unix uses one of these conflicting commands
to rewind the tape or maybe detect Digital Unix at the other end (I don't
remember).
and my original message was :
<---------->
Since any days, I have a strange problem dumping files with rdump.
This problem happened for all my remote boxes.
My script (which works well since a long time) is :
rsh sbgax9 /usr/sbin/rdump -0f sbgax4:/dev/nrmt0h -b 32 /usr
and I got the error message :
rdump: Dumping from host sbgax9.in2p3.fr
rdump: Date of this level 0 dump: Mon Feb 22 09:03:27 1999 GMT+0100
rdump: Date of last level dump: the start of the epoch=20
rdump: Dumping /dev/rrz0g (/usr) to /dev/nrmt0h on host sbgax4.in2p3.fr
rdump: Mapping (Pass I) [regular files]
rdump: Mapping (Pass II) [directories]
rdump: rmt reply(): Protocol to remote tape server botched (code OSF1
rdump: Communication error in connection to remote peer
rdump: SIGTERM received=20
rdump: The ENTIRE dump is aborted
rdump: SIGTERM received=20
rdump: The ENTIRE dump is aborted
<------->
So I didn't want to change all my scripts and move from
rdump to dump, I began to think about what I have modified
since the scripts stopped to work .....:(
The only modification I made was, under root, to change the
shell from sh to tcsh (using chsh tcsh). So, I went
back to sh (chsh sh) and now all works again well.
OK , now it works but I don't understand what could cause the
troubles .. ???
Thanks Jim
JEAN
-----------------------------------------------------------------------------
jean.schuller_at_ires.in2p3.fr _/ _/_/_/ _/_/_/ _/_/_/_/
_/ _/ -/ _/ _/ _/
_/ _/_/_/-/ _/_/_/ _/_/_/_/
_/ _/ -/ _/ _/
_/ _/ _/ _/_/_/ _/_/_/_/
local call: 0388106630 Institut de Recherches Subatomiques
foreign call: (33)388106630 Boîte Postale 28
local fax : 0388106234 23, Rue du Loess
foreign fax : (33)388106234 F-67037 STRASBOURG CEDEX - France
-----------------------------------------------------------------------------
Received on Wed Feb 24 1999 - 15:13:23 NZDT