Dave, did you leave out solution #4 for a reason?

        4. Turn off diskpool caching and delete the cached copies by doing
"move data" commands.

Wouldn't this be a solution, or are there times when you would still get
the error message?

A while back you (ADSM Dev.) changed the default for caching from yes to
no.  Does this indicate that disk caching is more trouble than it is worth?
What's your opinion on this?

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Re: Lotus Notes Client for Windows NT ... NOT!
02-06-1998 03:49 PM

Yes we are aware of the problem and it affects all client platforms. The
problem occurs when an incorrect size estimate of an object is sent to the
server.  The estimate is calculated incorrectly when a file grows during
compression (usually a file which is already compressed such as a .zip file)
and the size estimate contains the actual size of the file instead of the
larger amount of data which is actually sent (hence the estimate is to small).
We are currently working on a solution to this problem. For now, there are
several possible workarounds to the problem  (with possible undesirable side
effects):

   1. Exclude known compressed files from backup.  Downside is that critical
data may not be backed up, also may not be able to easily determine what files
are compressed.

 2.  Turn off COMPRESSALWAYS option . Downside is that performance will be
degraded in all clients because files which grow during compression will fail
and will be resent to the server uncompressed. Performance in version 3 servers
will also be degraded because file aggregation will not be as efficient when
failing files are resent.

3. Turn client compression off. Downside is that larger storage pool space on
the server will be required.


We hope to a solution to this problem soon.


Pete Tanenhaus
ADSM Client Development