On Mon, Nov 14, 2005 at 07:22:23PM +0100, Stefan G. Weichinger wrote: > Jon LaBadie wrote: > > >Might not be the last file on the tape. Suppose you collected things > >on the holding disk, possibly several days of dumps, before taping. > > > >If the metadata were to hold the DLE -> tape mappings, the dump of > >the metadata couldn't begin until after all other DLEs were taped. > >Does that raise any issues? > > The size of the metadata-DLE should be relatively predictable so this > amount of space could be put into calculation from start (also the > history should show what size to expect). The metadata-DLE could only be > dumped AFTER the regular DLEs are dumped completely and the related > indexes are written, so I assume the metadata-DLE simply gets into line > as soon as its ready.
What I was thinking was that many sites complete their dumping to holding disk well before taping is complete. For the metadata-DLE (MD-DLE?) to be complete it needs to know what tape(s) hold what DLE's. Thus dumping the MD-DLE would not only have to be last, but would have to be put on hold until all other taping was complete. It is the delay that I was concerned about. However I guess there is already precedence for such behavior by amdump. The starttime option, depending on the time argument, puts dumping on hold for a period. It resumes when triggered by the clock. Perhaps the MD-DLE could employ similar or the same code, but triggered by completion of all other activities. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
