Jon LaBadie wrote:
Might it be a good idea to have amtapetype note too many files
being written during the first phase and taking some action?
Maybe with an option to override the checking.
My idea was to write only one large file in the first pass, just
until it hits end of tape. Then rewind and write tapesize/100 files
to measure the size of a filemark.
That way you don't need to give an estimated tapesize at all.
Never got enough time to implement it though:
"Wife, children, house,... the full catastrophy" -- Zorba The Greek.
You ony have to look out for overflow while doing the math
for blocksize, speed etc. (200 Gbyte > 2^32 bytes)
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
