RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This BZ has been around since RHEL 5 and most of it was addressed a long time ago. I will get input from the gss team at this point to see if this is still a concern to document.

Ah, at long last I'm looking at the BZ and can see that it isn't the big deal I thought it was years ago when I first looked at this.  I think I can address this simply by noting how you can tell whether a dm table entry is open (and whether you can create a partition on it) -- noting when another program might have automatically created the partition already.

To get this off of the queue I'm moving this to RHEL 7 and should be able to finally address the issue with some embarrassment that it took this long. Once I get it in RHEL 7 and have it reviewed I can backport it to the RHEL 6 manual, but for now it will be RHEL 7.

Closing because I'm moving this to RHEL 7.

*** This bug has been marked as a duplicate of bug 1416898 ***