Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Under review
Workspace AIX
Created by Guest
Created on Aug 22, 2023

AIX kernel facility to track outstanding opens to a device

Currently AIX doesn't track open()s to a device. In case a process has a device opened before the configuration method has ran that device cannot be configured on the OS without a reboot, because it is not possible to identify the offending process.

I'd like to suggest that a facility be introduced to track outstanding open()s to a device - that would allow to identify the offending process and kill it to allow device configuration. 

This is a global issue, that has been seen by support in countless scenarios where a process on the host might open() a device before the driver (EMC PowerPath, MF Data Protector, etc...). Keeping the logging to only outstanding open()s should allow to keep the overhead tolerable as logging any open() would be quite a lot of workload.

For example scsidiskdd could track processes with an outstanding open() and store their PID in the disk major structure. That information could be retrieved by either "kdb -> scsidisk <address> or via a userspace tool for that.

Thank you for your consideration!

Idea priority Medium
  • Guest
    Aug 24, 2023

    AIX has a command line tool fuser that lists processes using specified file. Would it suffice for the purpose?