* Alexandre Oliva <[EMAIL PROTECTED]> (Fri, Apr 20, 2001 at 11:08:36AM -0300)
>> So it looks like amdump checks if there is enough space on the holding disk
>> before it starts dumping,
> Yep.
>> and then simply continues dumping whitout checking if the holding disk
>> becomes full, until it runs in a diskfull error and aborts the dump.
> It would fall over to another holding disk, if you had one.
>> The right thing (imo) would be to check every time a new chunk is written,
>> and if the chunk to be written would fail the holding disk free space
>> criteria, it should abort the dump.
> And end up aborting the dump anyway? What's the advantage?
1) it's quicker
Aborting a dump after 3 G has been written to disk,
or aborting after 4G has been written does make a difference.
2) It prevents diskfulls from happening, some other programs are suign the
disk for (very small) scratch space, and they fall over if the disk is
full (yes, I know, fix those programs ;) ) ...
3) The Right Thing (tm) if you have multiple hodling disks is t check
before starting to write the chunk whether you're below the watermark,
and if the next chunk would bring you below the watermark, switch to the
enxt holding disk.
No errors, no errors in the syslog.
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON.......#1 in Reservoir Characterization The Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
