Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!soma!concurrent-request
From: ben@it3.crl.mei.co.jp ([STL]Ben Reaves)
Newsgroups: comp.sys.concurrent
Subject: dump to stdout
Message-ID: <2487@gazette.bcm.tmc.edu>
Date: 1 Nov 90 02:27:24 GMT
Sender: usenet@bcm.tmc.edu
Lines: 27
Approved: concurrent@soma.neusc.bcm.tmc.edu
Nntp-Posting-Host: cortex.neusc.bcm.tmc.edu
Return-Path: <ben@it3.crl.mei.co.jp>

How can I send the dump output to stdout?

    "dump 0skouf 8200 - /dev/db0b | rsh microvax dd of=$tape"

Yielded only a file named - which was quite large!  Also, what should
the Block Size be (for the dd command on the microvax)?

I tried mounting the Masscomp (read "Concurrent") disk on a Sun
and dumping from the Sun side,
and got a nasty message about a Superblock Error -- and it refused to
do the dump.

I tried running tar on the Masscomp side and sent it to stdout by:

    "tar cf - . | rsh microvax dd obs=10240 of=$tape"

but when I tried "tar tv" on the microvax, it failed about halfway through the tape.


Any ideas? Workarounds? Fixes? Experiences?  
We are running RTU v4.0A.  Is it fixed in RTU v5.0?

				-- Ben Reaves

Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent
Administrative stuff: concurrent-request@soma.bcm.tmc.edu
Stan Barber, Moderator