CM 8.3 Threshold Issues on Suse 9

In Content Manager's Admin Client I have setup a File System Volume called
/dev/sda3 and set its Threshold to 10%. I am assuming this means that it will not fill this Volume past 10% of its capacity.

Next I created an overflow volume and left its Threshold at 100% and gave it an assignment to Overflow.

Both these volumes are set to be assigned to GROUP01.

Now when I try to ingest files the /dev/sda3 volume still fills to 100% of its capacity and does not stop at the 10% that I set it to. Once it hits 100% then the overflow volume kicks in and starts to ingest the files.

I?m not sure why it?s not stopping at 10%

I only have one guess and it is that the File System Volume is using the "ICMHDDM" Device Manager which is for Windows and I am using SUSE. I am not sure what device manager to use because none of them say they are specifically for Unix/Linux.

Please any suggestions are welcomed.

Thanks,
-Greg

gsarrica-at-us.ibm.com wrote:
> In Content Manager's Admin Client I have setup a File System Volume called
> /dev/sda3 and set its Threshold to 10%. I am assuming this means that it will not fill this Volume past 10% of its capacity.
>
> Next I created an overflow volume and left its Threshold at 100% and gave it an assignment to Overflow.
>
> Both these volumes are set to be assigned to GROUP01.
>
> Now when I try to ingest files the /dev/sda3 volume still fills to 100% of its capacity and does not stop at the 10% that I set it to. Once it hits 100% then the overflow volume kicks in and starts to ingest the files.
>
> I?m not sure why it?s not stopping at 10%
>
> I only have one guess and it is that the File System Volume is using the "ICMHDDM" Device Manager which is for Windows and I am using SUSE. I am not sure what device manager to use because none of them say they are specifically for Unix/Linux.
>
> Please any suggestions are welcomed.
>
> Thanks,
> -Greg
>
>

Hi Greg,

The volume threshold does not refer to how full the volume could get.
The volume threshold determines at what point the Migrator utility will
start moving objects from one storage class to the next storage class
defined in your migration policy. If there is storage available in your
secondary storage class, the space on the first filesystem will be
reduced to under 10%.

This documentation explains what each device manager is and what
platforms it can be used on.
http://publib.boulder.ibm.com/infoce...p/mos10026.htm

However it seems to be missing JFS (Journaled File System) and ICMVXFS
(Veritas File System) which can be used on UNIX filesystems. Not sure
about Linux though as I don't see anything that specifically calls it out.

Andy