--On Saturday, June 04, 2005 01:35:49 -0400 Jon LaBadie <[EMAIL PROTECTED]>
wrote:
> On Fri, Jun 03, 2005 at 10:46:30AM -0500, Frank Smith wrote:
>> --On Friday, June 03, 2005 10:14:50 -0500 "Erik P. Olsen" <[EMAIL
>> PROTECTED]> wrote:
>>
>> > On Fri, 2005-06-03 at 13:21 +0200, Paul Bijnens wrote:
>> >> Erik P. Olsen wrote:
>> >> > Hi,
>> >> >
>> >> > Could someone explain to me what the message below from amdump
>> > means?
>> >> > Especially the "fm 7 [OK]"
>> >>
>> >> fm = filemark: what a tape writes after a file.
>> >> [OK] means there were not errors so far.
>> >
>> > OK, not to be confused with no. of dumped files, I assume.
>>
>> Technically, it is the number of files written to to tape, but each
>> file is a dump image consisting of many source files, so think
>> of it as a count of the DLEs written to tape.
>>
>> >> > taper: tape DailySet103 kb 1131232 fm 7 [OK]
>
>
> Does taper adjust the reported number of filemarks for the
> tape header and trailer files it might write to the tape?
>
> I.e. is "fm" the number of DLEs written or is it off by
> 1 or 2 for the header and trailer files?
I looked at the output of one of my daily reports for a config
that fits on one tape, it reported a fm of 98 and there were 98
DLEs listed in the summary, so I suspect it really is just the
number of DLEs. Makes sense, since taper doesn't write the header
(it is already there from when it was labeled), and I don't think
there is a trailer file (but I have never checked to be sure).
On a two-tape config, the total fm's was one greater than the
number of DLEs, so it looks like the one that hit EOT was counted
twice.
I don't know if the tape-spanning dev version counts chunks or
DLEs as fm's, perhaps someone who uses it can check their reports
and find out.
Frank
>
> --
> Jon H. LaBadie [EMAIL PROTECTED]
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
--
Frank Smith [EMAIL PROTECTED]
Sr. Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
