-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "AMTAPETYPE" 8 "" "" ""
+.\" Title: amtapetype
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.72.0 <http://docbook.sf.net/>
+.\" Date: 02/07/2007
+.\" Manual:
+.\" Source:
+.\"
+.TH "AMTAPETYPE" "8" "02/07/2007" "" ""
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
.SH "NAME"
-amtapetype - generate a tapetype definition.
+amtapetype \- generate a tapetype definition.
.SH "SYNOPSIS"
.HP 11
-\fBamtapetype\fR [-h] [-c] [-o] [-b \fIblocksize\fR] -e \fIestsize\fR [-f \fItapedev\fR] [-t \fItypename\fR]
+\fBamtapetype\fR [\-h] [\-c] [\-o] [\-b\ \fIblocksize\fR] \-e\ \fIestsize\fR [\-f\ \fItapedev\fR] [\-t\ \fItypename\fR]
.SH "DESCRIPTION"
.PP
\fBamtapetype\fR
generates a tapetype entry for
-\fBAmanda\fR.
+\fIAmanda\fR.
.SH "OPTIONS"
-.TP
-\fB-h\fR
+.PP
+\fB\-h\fR
+.RS 4
Display an help message.
-.TP
-\fB-c\fR
+.RE
+.PP
+\fB\-c\fR
+.RS 4
Run only the hardware compression detection heuristic test and stop. This takes a few minutes only.
-.TP
-\fB-o\fR
+.RE
+.PP
+\fB\-o\fR
+.RS 4
Overwrite the tape, even if it's an
-\fBAmanda\fR
+\fIAmanda\fR
tape.
-.TP
-\fB-b\fR\fI blocksize\fR
+.RE
+.PP
+\fB\-b\fR\fI blocksize\fR
+.RS 4
record block size (default: 32k)
-.TP
-\fB-e\fR\fI estsize\fR
+.RE
+.PP
+\fB\-e\fR\fI estsize\fR
+.RS 4
estimated tape size (No default!)
-.TP
-\fB-f\fR\fI tapedev\fR
+.RE
+.PP
+\fB\-f\fR\fI tapedev\fR
+.RS 4
tape device name (default: $TAPE) The device to perform the test.
-.TP
-\fB-t\fR\fI typename\fR
-tapetype name (default: unknown-tapetype)
+.RE
+.PP
+\fB\-t\fR\fI typename\fR
+.RS 4
+tapetype name (default: unknown\-tapetype)
+.RE
.SH "EXAMPLE"
.PP
Generate a tapetype definition for your tape device:
.sp
+.RS 4
.nf
-
-% amtapetype -f /dev/nst0 -e 150G
-
+% amtapetype \-f /dev/nst0 \-e 150G
.fi
+.RE
.SH "NOTES"
.PP
Hardware compression is detected by measuring the writing speed difference of the tape drive when writing an amount of compressable and uncompresseable data. It does not rely on the status bits of the tape drive or the OS parameters. If your tape drive has very large buffers or is very fast, the program could fail to detect hardware compression status reliably.
.PP
-During the first pass, it writes files that are estimated to be 1% of the expected tape capacity. It gets the expected capacity from the -e command line flag, or defaults to 1 GByte. In a perfect world (which means there is zero chance of this happening with tapes :-), there would be 100 files and 100 file marks.
+During the first pass, it writes files that are estimated to be 1% of the expected tape capacity. It gets the expected capacity from the \-e command line flag, or defaults to 1 GByte. In a perfect world (which means there is zero chance of this happening with tapes :\-), there would be 100 files and 100 file marks.
.PP
During the second pass, the file size is cut in half. In that same fairyland world, this means 200 files and 200 file marks.
.PP
.PP
So if we wrote 1.0 GBytes on the first pass and 100 file marks, and 0.9 GBytes on the second pass with 200 file marks, those additional 100 file marks in the second pass took 0.1 GBytes and therefor a file mark is 0.001 GBytes (1 MByte).
.PP
-Note that if the estimated capacity is wrong, the only thing that happens is a lot more (or less, but unlikely) files, and thus, file marks, get written. But the math still works out the same. The -e flag is there to keep the number of file marks down because they can be slow (since they force the drive to flush all its buffers to physical media).
+Note that if the estimated capacity is wrong, the only thing that happens is a lot more (or less, but unlikely) files, and thus, file marks, get written. But the math still works out the same. The \-e flag is there to keep the number of file marks down because they can be slow (since they force the drive to flush all its buffers to physical media).
.PP
-All sorts of things might happen to cause the amount of data written to vary enough to generate a big 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.
+All sorts of things might happen to cause the amount of data written to vary enough to generate a big 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.
.PP
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
\fBamtapetype\fR
.SH "SEE ALSO"
.PP
\fBamanda\fR(8)
-
projects / debian / amanda / blobdiff