f

ftio(1)ftio(1)

NAME

ftio - faster tape I/O

SYNOPSIS

ftio -o⏐-O [achpvxAELM] [-B blksize] [-D type] [-e extarg] [-K comment] [-L ®lelist] [-N date®le] [-S script] [-T tty] [-Z nobufs] tapedev [pathnames] [-F ignorenames]

ftio -i⏐-I[cdfmptuvxAEMPR] [-Bblksize] [-Sscript] [-Ttty] [-Znobufs] tapedev [patterns]

ftio -g[v] tapedev [patterns]

DESCRIPTION

ftio is a tool designed speci®cally for copying ®les to tape drives. It performs faster than either cpio or tar in comparable situations (see cpio(1) and tar(1)). ftio uses multiple processes (to read/write the ®le system and to write/read the tape device), with large amounts of memory sharing between processes as well as a large block size for reading and writing to the tape.

ftio is compatible with cpio in that output from cpio is always readable by ftio, and output from ftio is readable by cpio, except as explained in the "cpio Compatibility" section, later in the manpage.

ftio must be invoked with exactly one of the following options: -o, -O, -i, -I, or -g. The -oand -Ooptions specify that ftio is writing "out" from ®le system to tape; the -iand -Ioptions specify that ftio is writing "in" from tape to ®le system. The -o, -O, -i, and -Ioptions can be followed by modi®ers that must appear immediately after the option with no spaces between the option and the modi®er, as in ftio -idxE(see Modi®ers section below).

tapedev speci®es the name of a device special ®le for the tape device to which the output is written. A device on a remote machine can be speci®ed in the form

machine:device_special_®le

ftio creates a server process from /usr/sbin/rmt on the remote machine to access the tape device. If /usr/sbin/rmt does not exist on the remote system, ftio creates a server process from /etc/rmt, on the remote machine to access the tape device.

Options

ftio recognizes the following options:

 

-o

Copy (out) ®les from the ®le system to tapedev, including path name and status infor-

 

mation.

If pathnames are speci®ed,

ftio recursively descends pathnames looking

 

for ®les,

and copies those ®les to tapedev. If pathnames are not speci®ed, ftio

 

reads the standard input to obtain a list of path names to copy. ftio can copy to

 

multiple tapes if required. For every tape used, ftio generates a tape header con-

 

taining the current tape volume number, machine node name and type, operating sys-

 

tem name, release and version numbers (all from the uname() system call; see

 

uname(2)), username of the person issuing the ftio command, the time and date the

 

command was executed, the number of consecutive times the current media has been

 

used, a comment ®eld, and other items used internally by ftio. The tape header is

 

separated from the main body of the tape archive by an end-of-®le mark. The tape

 

header can be read by invoking cat with the device ®le name as the ®rst argument

 

(see cat(1)). Note, character and block device special ®les written with the -ooption

 

are not transportable to other HP-UXimplementations.

-O

Copy out ®les in the same way as ftio -ocva, when no modi®ers are used with the

 

-O. However, if the .ftiorc ®le exists in the user's home directory, ftio opens

 

this ®le and scans for lines preceded by O=. Options de®ned on matching lines are

 

passed to ftio as if they had been speci®ed on the command line. See EXAMPLES

 

section.

 

 

-i

Extract (copy into the ®le system) ®les from tapedev, which is assumed to be a tape

 

and the product of a previous ftio

-ooperation. Only ®les with names that match

 

patterns,

according to the rules of Pattern Matching Notation (see regexp(5)), are

 

selected.

In addition, a leading ! within a pattern indicates that only those names

 

that do not match the remainder of the pattern should be selected. Multiple patterns

 

can be speci®ed. If no patterns are speci®ed, the default for patterns is * (that is,

 

select all ®les). The extracted ®les are conditionally created and copied into the

 

current directory tree, based upon the options described below. The permissions of

Section 1−290

 

− 1 −

HP-UX Release 11i: December 2000