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 (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 Not under consideration
Workspace AIX
Created by Guest
Created on Sep 26, 2017

Customer wants notification of when VGDA corruption occurs prior to a reboot of the system.

Action Taken:
- customer says he had vg on A and B, then they migrated to c and d and
brought it up fine.
- they a had shared luns and on one set of systems those luns had a vg
that was varied on and used. On the second set of system that had the
luns still mapped to them they accidentally added a new vg to those luns
and it corrupted the VGDA, customer says they were not notified no error
or any indication until later when the system was rebooted.
- The customer feels this is a design/code flaw and that there should
be a notification or error generated at the time of VGDA corruption
so that the user knows there is corruption.
Customer is wanting a design change request created for this
functionality to be implemented
- Due to the fact that they did not know for awhile that the VGDA
had been corrupted they continued to use the VG on the other system
until they tried to bring it down and backup was the only indication
at that point that they had a problem

Idea priority Low
  • Guest
    Reply
    |
    Apr 9, 2020

    LVM already have the functionality to protect against over writing existing VG on disk.
    If a user tries to create a new volume group on a disk containing an existing volume group, mkvg prints a warning message that says the disk appears to belong to another VG and use force option to overwrite the VG. It is users responsibility to check the disk before using the force option. Local system doesn't know if someone overwrites VG/data on the disk from a different system.

  • Guest
    Reply
    |
    Sep 27, 2017

    If a user tries to create a new volume group on a disk containing an existing volume group, mkvg will give them an error telling them there is already a vg on it:

    # mkvg -y testvg hdisk20
    0516-1398 mkvg: The physical volume hdisk20, appears to belong to
    another volume group. Use the force option to add this physical volume
    to a volume group.
    0516-862 mkvg: Unable to create volume group.

    The only way to create a new volume group on a disk with an existing volume group is to use the force option to mkvg (-f). In my opinion the user assumes any risk he takes using the force option, as the regular option will error out and not create the vg.

    It looks like in this customer's case the VGDA was not "corrupt", it was overwritten.