Skip to Main Content
IBM System Storage Ideas Portal

This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories HSM for Windows
Created by Guest
Created on Aug 31, 2011

Implement recall thread timeout on HSM service driver.

Explanation first:

Whenever a file is recalled on the OS file system level (e.g. double clicked in explorer) this sets of a driver call defined by the reparse point definition in the "STUB" file. This causes the kernel mode driver to request the HSM service to perform a recall, which is initiated at this time.

There are x number of concurrent recall threads.

At the current point in time, there are no timeout on the recall threads. If the TSM server misbehaves, and do not deliver data, and at the same time does not bail out with an error, the recall thread is stuck forever.

In the above mentioned scenario, further recall requests beyond the x number of concurrently running recall threads are queued up, and all those request have kernel references (because the filesystem level driver triggered by the reparse point call, carries a reference from the kernel mode process to the user mode process responsible for performing the recall).

If all x conccurent recall threads gets stuck in this unfortunate mode, recall requests will build up until the point where the kernel non-paged memory pool is exhausted due to the high number of kernelmode <--> usermode references, and the server bluescreens because of this.

Apparantly there is a cleanup routing to kill off stuck threads, however this routing is only triggered after a thread successfully returns, so if all threads gets stuck within the time limit where a thread is considered stuck, then there is no further control mechanisms to avoid recall queue buildup.

This is clearly to be considered a bug, but apparantly there is no bug reporting mechanism to this product, so here we go with an "enhancement" request.


Create a control mechanism which monitors recall threads, or change the way recall threads run, so that a timeout is enforced on recall operations. Any recall threads exceeding the defined timeout is then terminated and cleaned up, so as to avoid killing the server by exhausting the kernel nonpaged memory pool.

Idea priority Urgent
  • Guest
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Sep 14, 2011

    Thank you for submitting this enhancement request, we do understand the requirement and the rationale behind it but unfortunately we currently do not plan to implement this enhancement request. the current logic HSM uses is that if someone tried to recall a file the expected result is that the file will be restored (unless an error happens) if we decide to follow the suggested enhancement it might cause multiple failures for reasons that are not related to the HSM functionality without user interaction.