]> sourceware.org Git - lvm2.git/commit
In the new _vg_read_for_update(), we always do the check for CLUSTERED vg
authorDave Wysochanski <dwysocha@redhat.com>
Wed, 10 Jun 2009 16:14:40 +0000 (16:14 +0000)
committerDave Wysochanski <dwysocha@redhat.com>
Wed, 10 Jun 2009 16:14:40 +0000 (16:14 +0000)
commit8e95a2a603dc7cb181cf9a50a557bacc4a0d3012
tree7eb7a750ffc537f209ed66cf9cce85ff999325f2
parent6a1c94d48da5e13023c5040461c468cfaa2bdd5e
In the new _vg_read_for_update(), we always do the check for CLUSTERED vg
status flag after reading the volume group.  Thus, no need to set the flag
in vg_read() or clear it later before calling _vg_bad_status_bits().

Also, add back in the !lockingfailed() as part of the CLUSTERED flag check.
It's unclear why it was removed when the check was moved from
_vg_bad_status_bits() to inside _vg_lock_and_read().
There was an open question about the last check in the 'if' stmt for
lockingfailed() with a previous patch submitted.  However, I would
defer that right now as it is a separate item and this patch should
be no functional change by including the !lockingfailed().

Petr acked this patch on 5/26 I just forgot to check it in.

Acked-by: Petr Rockai <prockai@redhat.com>
lib/metadata/metadata.c
This page took 0.035678 seconds and 5 git commands to generate.