diff options
| author | Jonathan Earl Brassow <jbrassow@redhat.com> | 2012-04-26 17:30:49 +0000 |
|---|---|---|
| committer | Jonathan Earl Brassow <jbrassow@redhat.com> | 2012-04-26 17:30:49 +0000 |
| commit | e5b9338ada7152672000016861ef06f4af2160aa (patch) | |
| tree | 44d9767addcf091253b57dbf50d2ecff28c25c43 /WHATS_NEW | |
| parent | 34fbbfe34ee2251cc95263e27c5282d125f47779 (diff) | |
| download | lvm2-e5b9338ada7152672000016861ef06f4af2160aa.tar.gz lvm2-e5b9338ada7152672000016861ef06f4af2160aa.tar.xz lvm2-e5b9338ada7152672000016861ef06f4af2160aa.zip | |
Fix bug in cmirror that caused incorrect status info to print on some nodes.
Looking at the code in cmirrord/local.c, we can see the various different
request types handled in different ways. Some information that is non-changing
does not need to go around the cluster and can be short-circuited. For
example, once the cluster mirror is in-sync, it is pointless to continue
sending that query around the cluster. We can save network bandwidth and reply
directly back to the kernel. When it comes to status information, there are
two types 'TABLE' and 'INFO'. The 'TABLE' information never changes and
belongs to the group of requests that can be safely short-circuited. The
'STATUS' information can change - and will change if a device fails. Thus it
cannot be short-circuited, but this is exactly what was found. The 'STATUS'
information request was being short-circuited and therefore never reporting the
failure condition to anyone other than the "server" that experienced it
directly.
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.02.96 - ================================ + Fix bug in cmirror that caused incorrect status info to print on some nodes. Remove statement that snapshots cannot be tagged from lvm man page. Disallow changing cluster attribute of VG while RAID LVs are active. Fix lvconvert error message for non-mergeable volumes. |