🚀 go-pugleaf

This may sound like a dumb question, but I haven't done this before in
this particular environment.  I started a full backup onto TK50s of a
/usr filesystem on a MicroVAX-II running Ultrix 3.0.  When it asked for
a second tape, I inserted it, waited until it was on-line and typed
"yes" to the dump program.  Rather than immediately proceeding to write
on the second tape, the program simply ran and ran, chalking up CPU
time without touching the tape.  There was no doubt about my typing the
"yes" and the program no longer waiting for terminal input.  Since I
was pressed for time, I didn't let it run beyond 10 minutes (of
accumulated CPU).  The backup is, of course, incomplete.

Just to be sure this wasn't pilot error, I repeated this with
the same results.

Is this normal?  Is this a bug (fixed in a later Ultrix 3.x
release?)  Dump to TK50s under 4.3BSD on a VAX performs as
expected when another tape is required (i.e., it starts
writing to the second tape almost immediately.)

---
Steve Dyer
dyer@ursa-major.spdcc.com aka ...!{harvard,linus,ima,m2c,rayssd}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu