mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-29 12:03:03 +00:00
107 lines
3.6 KiB
Groff
107 lines
3.6 KiB
Groff
.\" Copyright (c) 1985, 1990, 1991, 1993
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
.\" must display the following acknowledgement:
|
|
.\" This product includes software developed by the University of
|
|
.\" California, Berkeley and its contributors.
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
.\" may be used to endorse or promote products derived from this software
|
|
.\" without specific prior written permission.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" @(#)tcopy.1 8.2 (Berkeley) 4/17/94
|
|
.\" $FreeBSD$
|
|
.\"
|
|
.Dd April 17, 1994
|
|
.Dt TCOPY 1
|
|
.Os BSD 4.3
|
|
.Sh NAME
|
|
.Nm tcopy
|
|
.Nd copy and/or verify mag tapes
|
|
.Sh SYNOPSIS
|
|
.Nm
|
|
.Op Fl cvx
|
|
.Op Fl s Ar maxblk
|
|
.Oo Ar src Op Ar dest
|
|
.Oc
|
|
.Sh DESCRIPTION
|
|
.Nm Tcopy
|
|
is designed to copy magnetic tapes. The only assumption made
|
|
about the tape is that there are two tape marks at the end.
|
|
.Nm Tcopy
|
|
with only a source tape
|
|
.Pf ( Ar /dev/rsa0
|
|
by default) specified will print
|
|
information about the sizes of records and tape files. If a destination
|
|
is specified a copy will be made of the source tape. The blocking on the
|
|
destination tape will be identical to that used on the source tape. Copying
|
|
a tape will yield the same output as if just printing the sizes.
|
|
.Pp
|
|
Options:
|
|
.Bl -tag -width s_maxblk
|
|
.It Fl c
|
|
Copy
|
|
.Ar src
|
|
to
|
|
.Ar dest
|
|
and then verify that the two tapes are identical.
|
|
.It Fl s Ar maxblk
|
|
Specify a maximum block size,
|
|
.Ar maxblk .
|
|
.It Fl v
|
|
Given the two tapes,
|
|
.ar src
|
|
and
|
|
.Ar dest
|
|
verify that they are identical.
|
|
.It Fl x
|
|
Output all informational messages to the standard error.
|
|
This option is useful when
|
|
.Ar dest
|
|
is
|
|
.Pa /dev/stdout .
|
|
.El
|
|
.Sh SEE ALSO
|
|
.Xr mtio 4
|
|
.Sh HISTORY
|
|
The
|
|
.Nm
|
|
command appeared in
|
|
.Bx 4.3 .
|
|
.Sh BUGS
|
|
Writting an image of a tape to a file does not preserve much more than
|
|
the raw data. Block size(s) and tape EOF marks are lost which would
|
|
otherwise be preserved in a tape-to-tape copy.
|
|
|
|
EOD is determined by two sequential EOF marks with no data between.
|
|
There are old systems which typically wrote three EOF's between tape
|
|
files.
|
|
.Xr tcopy 1
|
|
will erroneously stop copying early in this case.
|
|
|
|
When using the copy/verify option \-c
|
|
.Xr tcopy 1
|
|
does not rewind the tapes prior to start. A rewind is performed
|
|
after writing prior to the verification stage. If one doesn't start
|
|
at BOT then the comparison may not be of the intended data.
|