• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Delete STGpooldir with unavailable containers

blankgap

ADSM.ORG Member
Joined
Jun 5, 2018
Messages
51
Reaction score
2
Points
0
Hi,

a few weeks ago we had an incident where a co-worker unintentionally damaged some containers in 2 of our 31 containerpool-directories, but lets focus on just one, the last of them (Directory31)
I managed to get rid of most of the damaged containers, moved all the data to other directories and updated the stgpooldir to access=destroyed

q stgpooldir

DEDUPPOOL D:\STG\DR\Container31 Destroyed



Unfortunately, there are 3 containers remaining in this directory:

q container state=unavailable

D:\STG\DR\Container31\14\00000000000014cb.dcf DEDUPPOOL Dedup Unavailable
D:\STG\DR\Container31\24\0000000000002426.dcf DEDUPPOOL Dedup Unavailable

D:\STG\DR\Container31\39\00000000000039e6.dcf DEDUPPOOL Dedup Unavailable

Does anyone have an advice on how to get rid of these 3 remaining containers?
The Reusedelay on the stgpool is set to 0 (temporary) and if I issue "audit container <containername> action=removedamaged", the process finishes successfully, but the containers are not removed.
These containers do not even exist in the filesystem anymore (The directories 14, 24 and 39 don't exist in Container31 Mountpoint)

I really need to delete this stgpooldir to reuse the diskspace mounted on it, but even after a week with reusedelay=0, TSM just won't remove those containers and it's not possible to delete the stgpooldir with remaining containers in it.

Any help would be appreciated.

Kind regards
 

MvtLoo

Newcomer
Joined
Mar 22, 2020
Messages
1
Reaction score
0
Points
0
Location
Europe
Website
mvantloo.nl
> I really need to delete this stgpooldir to reuse the diskspace mounted on it

If you are really sure that there is no data anymore on this mount-point, you can remove it already at filesystem level and reuse the space.
Of course you still will have some dirt within SP, but at least you can continue with your storage needs.

From my experience, sometimes it takes some hours (or even until the next day) before background processes within SP are finished. So also just wait another day and see if the volumes disappear by itself.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,615
Reaction score
578
Points
0
Location
Canada
Website
www-947.ibm.com
You can see with the Query EXTENTUPDates how many extents are left to delete from the database.

When deleting containers, the server has a lot of work to do. The server needs to identify all the extents on that container, then identify which files they belong to, then delete that file also from the database, then check all the extents that belong to that file and determine if they are shared with other files. If shared with other files, they are kept, if not, also discarded. If the database layout or disks are subpar, that process will also take longer to do.
 

blankgap

ADSM.ORG Member
Joined
Jun 5, 2018
Messages
51
Reaction score
2
Points
0
> I really need to delete this stgpooldir to reuse the diskspace mounted on it

If you are really sure that there is no data anymore on this mount-point, you can remove it already at filesystem level and reuse the space.
Of course you still will have some dirt within SP, but at least you can continue with your storage needs.
Unfortunately I can't really reuse the space on the TSM-Server, as I don't want to create a new stgpooldir #32 when stgpooldir #31 is still defined and can't be deleted (because there are containers in it)


When deleting containers, the server has a lot of work to do. The server needs to identify all the extents on that container, then identify which files they belong to, then delete that file also from the database, then check all the extents that belong to that file and determine if they are shared with other files. If shared with other files, they are kept, if not, also discarded. If the database layout or disks are subpar, that process will also take longer to do.
I understand that there is a lot of workload on the database. But those containers are stuck at "unavailable" for multiple weeks now, so I think there should have been enough time for the Server to remove them.

I will post an update, if there is one.
 

blankgap

ADSM.ORG Member
Joined
Jun 5, 2018
Messages
51
Reaction score
2
Points
0
What does the Query EXTENTUPDates command report?
Output of Query extentupdate:
Unbenannt.PNG


Also, I tried to use action=markdamaged before action=removedamaged
But it doesn't delete any extents:
ANR3729I The AUDIT CONTAINER command process 2232 completed:
0 damaged objects are deleted.
0 damaged objects are skipped.
0 dependent objects are deleted.
0 orphan objects are deleted in cloud-container storage.
0 orphan objects are skipped in cloud-container storage pools
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.2%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 61.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.1%
  • Other (please comement)

    Votes: 8 8.1%

Forum statistics

Threads
31,750
Messages
135,360
Members
21,746
Latest member
NasriSaleh
Top