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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Enhancement requested to restrict/regulate accidental provisioning of same disk (storage LUN) to multiple nodes at volume manager level(LVM) :
In a customer environment multiple servers ,multiple LPAR's are managed by a SAN/NAS backed storage. It's being observed that a disk/LUN/Physical-Volume that is provisioned to a system/node is being presented/provisioned to another system/node as a fresh disk .
This being done by customer accidentally/by mistake/typo/unknowingly or sometimes with lack of knowledge.
System logs captures only the details of the system/Node and no idea on its storage mapping of other Node's it will be hard to debug many file system corruption and Volume manager metadata corruption cases. When the other System/Node corruption issue observed , then its realized that both are related and can conclude that same disk was presented on both the Node's that caused the corruption on both Node's VG's.
Thus request the enhancement to prevent this scenario happening at Volume Manager's level
which gives admin error/warning with information about other Node(s) where the disk/LUN presented.
Thus admin has to check back their storage mapping configurations to prevent this scenario.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.