Delete filespace simply deletes database entries and does not directly
cause allocation or mounting of volumes.  I believe that something else must
have been running at the same time as the Delete Filespace.  For example,
maybe the Filespace Deletion triggered reclamation or perhaps migration
was moving files into this storage pool.

Dave Cannon
ADSM Development
--------------------------------------------------------------------
I have done a DELETE FILESPACE for one of our nodes to purge all the backed up 
date. This however causes ALL volumes to be allocated
I have done a DELETE FILESPACE for one of our nodes to purge all the backed up 
date. This however causes ALL volumes to be allocated
and then deleted!!
Why does ADSM allocate the volumes???? It should just update it's databases so 
the data isn't referenced anymore and then deleted
during an normal client file space expiration process.
We use collocation so all volumes include data from just one client. Which all 
expires at once so no allocation should be necessary.
Even if collocation is off a allocation shouldn't be necessary because just the 
reference to the actual data (in the ADSM server
databases) is removed. This way numerous unwanted volume mounts occur!
Can somebody explain this?
Thanks in advance!
Kind regards,
Eric van Loon