Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

amtapetype(8) [centos man page]

AMTAPETYPE(8)						  System Administration Commands					     AMTAPETYPE(8)

NAME
amtapetype - generate a tapetype definition by testing the device directly SYNOPSIS
amtapetype [-h] [-c] [-f] [-p] [-b blocksize] [-t typename] [-l label] [-o configoption...] [config] [device] DESCRIPTION
amtapetype generates a tapetype entry for Amanda by testing the device directly. OPTIONS
Note The options for amtapetype have changed in version 2.6.1 -h Display the help message. -c Run only the hardware compression detection heuristic test and stop. This takes a few minutes only. -f Run amtapetype even if the loaded volume is already labeled. -p Run only the device property discovery. -b blocksize block size to use with the device (default: 32k) -t typename Name to give to the new tapetype definition. -l label Label to write on the tape (default is randomly generated). -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). If a configuration is specified, it is loaded and used to configure the device. Note that global configuration parameters are not applied to the device, so if you need to apply properties to a device to run amtapetype, you should supply those properties in a named device section. EXAMPLE
Generate a tapetype definition for your tape device: % amtapetype -f /dev/nst0 NOTES
If the device cannot reliably report its comprssion status (and as of this writing, no devices can do so), hardware compression is detected by measuring the writing speed difference of the tape drive when writing an amount of compressable and uncompresseable data. If your tape drive has very large buffers or is very fast, the program could fail to detect hardware compression status reliably. Volume capacity is determined by writing one large file until an error, interpereted as end-of-tape, is encountered. In the next phase, about 100 files are written to fill the tape. This second phase will write less data, because each filemark consumes some tape. With a little arithmetic, amtapetype calculates the size of these filemarks. All sorts of things might happen to cause the amount of data written to vary enough to generate a strange file mark size guess. A little more "shoe shining" because of the additional file marks (and flushes), dirt left on the heads from the first pass of a brand new tape, the temperature/humidity changed during the multi-hour run, a different amount of data was written after the last file mark before EOT was reported, etc. Note that the file mark size might really be zero for whatever device this is, and it was just the measured capacity variation that caused amtapetype to think those extra file marks in pass 2 actually took up space. SEE ALSO
amanda(8), amanda.conf(5) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Jean-Louis Martineau <martineau@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.3 01/10/2013 AMTAPETYPE(8)

Check Out this Related Man Page

AMDEVCHECK(8)						  System Administration Commands					     AMDEVCHECK(8)

NAME
amdevcheck - Validate an Amanda device and volume. SYNOPSIS
amdevcheck [--label] [-properties list] [-o configoption...] config [device-name] DESCRIPTION
Amdevcheck provides a way to check that a particular Amanda device is accessible, whether or not it contains a volume, and whether or not that volume is labeled. Some devices can't distinguish between all of these cases; a missing volume and an unlabeled volume might generate the same error code, for example. In those cases, this tool reports all possible causes of the error. Optionally this tools lists the properties for the device. See the amanda(8) man page for more details about Amanda. See amanda-devices(7) for more information on devices. OPTIONS
config Amanda configuration to use. Note that amdevcheck ignores any tape changer configuration. device Amanda device to use. This option overrides any tapedev configuration specified in the configuration file. --label Get the device's label. If this option is given, the usual check output is omitted, and the label of the loaded volume is printed to stdout. Returns with error if the label is not found. --properties [list] List device properties. If this option is given, the usual check output is omitted, and property values are printed to stdout, one per line, as a property name, followed by '=', followed by the property value. Returns with error if properties are not available. If list is given, it is treated as a comma-separated list of properties to display. If it is omitted, all supported properties are displayed. -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). OUTPUT
amdevcheck exit with code 0 if the device is working of if it get an expected error, look at the MESSAGE line for the error. It exit with code 1 if it get an unexpected error. Amdevcheck returns one or more of the following lines. If multiple lines appear, then at least one, but not necessarily all of the messages apply. This situation can occur when working with hardware or operating systems which cannot distinguish, for example, between a malfunctioning drive and a functional but unloaded drive. SUCCESS A tape is ready. DEVICE_ERROR A device error has occurred. DEVICE_BUSY The device is busy. VOLUME_MISSING No tape is loaded in the drive. VOLUME_UNLABELED The tape in the drive is unlabeled. VOLUME_ERROR A volume error has occurred. MESSAGE text Where text provides a human-readable description of the problem. SEE ALSO
amanda(8), amanda-devices(7) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHOR
Ian Turner <ian@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.3 01/10/2013 AMDEVCHECK(8)
Man Page