We use a TSM instance (version 6.2) for archiving mail attachments. This instance has its own storage system that provides the storage available.
In TSM, a sequential device class is created, with the paths of the LUN's storage system. The storage pool is a primary pool is defined. The volumes are each 20 GB in size. The problem we have: There are always created volumes that only 0.1% are then fully. The next letter mail attachments in the pool new volumes will be reinvested, which are again occupied only 0.1%. So we now have hundreds of volumes that are full only to 0.1%. These volumes are then marked with "full" status.
Below are two overviews (screenshots) of the affected volumes.
Any idea where the problem could be?
In TSM, a sequential device class is created, with the paths of the LUN's storage system. The storage pool is a primary pool is defined. The volumes are each 20 GB in size. The problem we have: There are always created volumes that only 0.1% are then fully. The next letter mail attachments in the pool new volumes will be reinvested, which are again occupied only 0.1%. So we now have hundreds of volumes that are full only to 0.1%. These volumes are then marked with "full" status.
Below are two overviews (screenshots) of the affected volumes.
Any idea where the problem could be?