This looks like APAR IC29607.  Here is the closing text.


**************************************************************
* USERS AFFECTED:
All TSM V3.7.0 and TSM V4.1.0 servers.
**************************************************************
* PROBLEM DESCRIPTION:
Move Data within the same DISK stgpool does not always move
everything.
**************************************************************
* RECOMMENDATION:
Apply fixing PTF when available.
**************************************************************
Move Data within the same DISK stgpool, sometimes does not
move all the data.  This occurs when the data "grew" during
initial backup or if the size estimate sent by the client
was too low.  Incorrect size estimates cause the file to be
stored in multiple segments in the DISK stgpool.  Moving
within the same stgpool was not handling these other segments.
Move Data within the same DISK stgpool has been updated to
correctly handle multi-segment bitfiles.
Customers can issue Move Data command(s) against the volume
until the volume is empty.  Alternatively the customer can
move the volume to a temporary sequential stgpool, update the
DISK volume access=readonly to ensure the original volume stays
empty, then Move Data back to the DISK stgpool.


Dave Cannon
Tivoli Storage Manager Development
Tivoli Systems, IBM Corporation
dcannon AT us.ibm DOT com
Tie-line: 321-4052     Phone: (520)799-4052


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  Can't empty diskpool volumes!?!


Hi *SM-ers!
I'm moving my diskpool to new disks.
I added the new disks to the diskpool and I updated the old disk volumes to
read-only. Then I started a move data to empty the old volumes. The move
data works fine, but at the end (with a completion state of SUCCESS) there
is still data left on the volumes! I can't get rid of this data and thus I
can't delete the old volumes!
Does anybody know how to solve this?
Thanks in advance for any reply!!!
BTW: I'm running TSM 3.7.4 on AIX 4.3.3.50
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines