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 bug has been copied from bug #882276 and has been proposed
to be backported to 6.3 z-stream (EUS).

commit 2ba76e3b45a9866b913ece63a51c540410fdd561
Author: Federico Simoncelli <fsimonce>
Date:   Mon Dec 3 05:28:39 2012 -0500

    upgrade: reallocate the metadata slots when needed

http://gerrit.ovirt.org/#/c/9660/

Federico, please review the "Doc Text" to ensure that it accurately reflects the change.

The "Doc Text" is accurate.

verified on si25.1

I installed vdsm 4.9.105 and created lv's
upgraded to latest 3.0 vdsm 
upgraded to latest 3.1 vdsm 
upgraded cluster/dc. 

md output before the vdsm upgrade: 

[root@gold-vdsd ~]#  lvs -o +tags | sed -n 's/.*MD_\([0-9]\+\).*/\1/p' | sort -n | tail
3072
3584
4096
4608
5120
5632
6144
6656
7168
7680


after upgrade: 

[root@gold-vdsd ~]#  lvs -o +tags | sed -n 's/.*MD_\([0-9]\+\).*/\1/p' | sort -n | tail
6
7
8
9
10
11
12
13
14
15

no error from sanlock were detected.

*** Bug 889579 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0159.html