Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!gvgpsa!davew
From: davew@gvgpsa.GVG.TEK.COM (David C. White)
Newsgroups: comp.unix.ultrix
Subject: Re: Dumping multiple partitions to a single tape.
Keywords: Dump Single Tape
Message-ID: <1353@gvgpsa.GVG.TEK.COM>
Date: 26 Feb 90 17:41:11 GMT
References: <1990Feb20.054208.17932@ncsuvx.ncsu.edu> <1990Feb21.051622.10343@ncsuvx.ncsu.edu> <1344@gvgpsa.GVG.TEK.COM> <671@parcplace.com>
Distribution: usa
Organization: Grass Valley Group, Grass Valley, CA
Lines: 26

In article <671@parcplace.com> khaw@parcplace.com (Mike Khaw) writes:
>+In article <1990Feb21.051622.10343@ncsuvx.ncsu.edu> map@cscosl.ncsu.edu (Mark Parris) writes:
>+There is an easy workaround for this one.  For your last dump use
>+the rewind device and the tape will rewind automatically when
>+the dump is complete.
>
>If dump behaves like tar, then this will cause the tape to rewind to
>BOT *before* dumping the last filesystem, thus destroying your earlier
>dump(s).

Haven't really tried it with tar,  but it works as it should with
dump.  The tape should not rewind until after the current operation.
You want to the the norewind device for all but the last dump.  From
mtio(4):

     The special files ``rmt0l, ..., rmt31l'' are low density,
     ``rmt0m, ..., rmt31m'' are medium density (when a drive is
     ``triple density''), and ``rmt0h, ..., rmt31h'' are high
     density. All these special files cause a loaded and on-line
     tape to automatically rewind to the beginning-of-tape (BOT)
     when closed.
     ^^^^^^^^^^^
-- 
Dave White	Grass Valley Group, Inc.   VOICE: +1 916.478.3052
P.O. Box 1114  	Grass Valley, CA  95945    FAX: +1 916.478.3887
Internet: davew@gvgpsa.gvg.tek.com     UUCP:  ...!tektronix!gvgpsa!davew