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 ``\fBshoe shining\fR'' 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 to think those extra file marks in pass 2 actually took up space\&.
projects / debian / amanda / blobdiff