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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Feb 6, 2026

Identify nodes having open files which blocks quiesce file system/filesets

We had the situation that the unlink fileset command failed:

[root@xstm-d07-01 samples]# mmunlinkfileset exa_project1 training2601 -f
Unable to quiesce fileset at all nodes.
Fileset training2601 has open files. Specify -f to force unlink.
mmunlinkfileset: Command failed. Examine previous error messages to determine cause.

But we were not able to identify in this situation, which of the 2800 client node was the root cause (or may be multiple of them).

  • no waiters in the storage cluster
  • no waiters on the client nodes

Se we were forced to create traces on the storage cluster and asked the support to check them. They told us the node which was the root cause. We checked it, rebooted this node and the situation was solved.

So what we need in this kind of situations is to have a tool at hand (e.g. mmdiag or mmfsadm dump) which would give us some information of open file handle of target file system/fileset.

Or the mmunlink command (and every other command which trigger a quiesce) will report the node(s) which block the operation.

Idea priority Medium