Hi Folks,
First of all, happy new year to all of you !
I do experience a strange behavior with container based storage pools, which I
would like to share with you. Basically it's all about wasted space in
directory pools, which I would like to reclaim :
1) I do search for some container having "max size"="free space", so
basically an empty container ...
Protect: CH2LX770>q container
/tsm/IsilonCOLO/sf/sfisi/StrgPool-3/vm/15/01/00000000000115aa.dcf f=d
Container:
/tsm/IsilonCOLO/sf/sfisi/StrgPool-3/vm/15/01/00000000-
000115aa.dcf
Storage Pool Name: DIR_VM
Container Type: Dedup
State: Available
Free Space(MB): 10,323
Maximum Size(MB): 10,323
Approx. Date Last Written: 08/25/2018 01:30:54
Approx. Date Last Audit:
Cloud Type:
Cloud URL:
Cloud Object Size (MB):
Space Utilized (MB):
Data Extent Count:
2) I then start a "move container", using the "defrag=yes" option :
Protect: CH2LX770>move container
/tsm/IsilonCOLO/sf/sfisi/StrgPool-3/vm/15/01/00000000000115aa.dcf defrag=yes
ANR0984I Process 15195 for Move Container started in the BACKGROUND at 11:44:42
AM.
3) This is what the activity log reports :
Date/Time Message
--------------------
----------------------------------------------------------
01/10/2019 11:44:42 ANR0984I Process 15195 for Move Container started in the
BACKGROUND at 11:44:42 AM. (SESSION: 339756, PROCESS:
15195)
01/10/2019 11:45:27 ANR0986I Process 15195 for Move Container running in the
BACKGROUND processed 42,742 items for a total of
1,695,019,008 bytes with a completion state of SUCCESS
at 11:45:27 AM. (SESSION: 339756, PROCESS: 15195)
So basically a container reported as being empty is not in reality ? Shall I
assume that this is a bug ?
BTW, spectrum protect server 8.1.4 running on PowerLinux.
Cheers.
Arnaud
