In article <20000227042617.96337.qmail AT hotmail DOT com>, Alyn Bush
<alynbush AT HOTMAIL DOT COM> says:
>
>Hi all,
>Even though I think I have enough storage space still some times I get "
>Server out of data storage space" messages.  Recently again I got following
>message for this file:
>-rw-r--r--   1 root       sys        161986560 Feb 27 06:21 pl6_runner.tar
>This is the message I'm getting:
>"02/25/00   05:18:12 ANS1311E Server out of data storage space"
>Thanks,
>Alyn
>

Hello Alyn

This may be one of the long running problems the *SM developers
have been asked to fix.

Do you have caching turned on for your storage pools? Do have by
default or by explicit option have the compressallways option turned
on? The default for this option was changed from no to yes at one
of the past levels.

As I know it, what happens is that at the start of the backup
for the file, the server reserves enough space in the storage pool
to hold the file based on the clients estimate. If storage pool
caching is turned  on then cached entries have to be released.
If the system can not reserve enough space for the file in the
storage pool then it is stored on the next storage pool that has
room for the file. Normally  at least one storage pool is defined with
no size limit, so this normally works.

Then the file is transmitted up to the server. If it is not compressed
or reduces in size with compression it is stored in the reserved
space and all is ok. If the file grows in size with compression and
compressallways is not set then the client will stop sending the
file and retransmit without compression and all is ok. But if
compressionallways is set the file will be transmitted until the
reserved space is used up. After that time the server out of message
is issued if there is no free space in the storage pool. Without
caching there is normally free space, but with caching the storage
pool is full by design. It would be nice if the client could wait for
the server to find more space in the storage pool or one of the next
storage pools and then continue the backup.

/len