diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2015-09-15 17:38:02 +0200 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2015-09-15 18:07:32 +0200 |
| commit | fcfca57e2e15c5cae3ccac225669d97c65b6b9db (patch) | |
| tree | d8d4df84da2a36baf42d2d24b2036d1c38fedb7f | |
| parent | 0ac10bb23a9e356b87ead9e1304a6482f6761b9b (diff) | |
| download | lvm2-fcfca57e2e15c5cae3ccac225669d97c65b6b9db.tar.gz | |
format-text: label: fix missing dev assignment for struct label in _text_pv_write
When using lvm shell, some structures which are cached in memory may be
reused. This happens for the struct label (a part of lvmcache_info
structure) when lvmetad is used in which case the PV scan is not
done that would normally overwrite these label structures in memory
and making them up-to-date.
This is all consequence of the fact that struct lvmcache_info and
struct label are not always assigned in the same part of the code.
For example, if lvmetad *is not* used, parts of the struct label are
reassigned in label_read fn while struct lvmcache_info is created
elsewhere. No part of the code reused struct label (and its "dev"
field) before calling label_read fn. That's why the real bug is
hidden when using lvm shell without lvmetad.
However, with lvmetad and lvm shell, the situation is a bit different.
The label_read fn is not called if lvmetad *is* used, hence the
struct label may have ended up not initialized properly.
There was missing assignment for the dev field in struct label
in _text_pv_write fn which caused this problem to appear in
lvm shell with lvmetad, for example:
Before this patch:
lvm> pvcreate /dev/sda
Physical volume "/dev/sda" successfully created
lvm> pvs /dev/sda
PV VG Fmt Attr PSize PFree
unknown device lvm2 --- 128.00m 128.00m
With this patch applied:
lvm> pvcreate /dev/sda
Physical volume "/dev/sda" successfully created
lvm> pvs /dev/sda
PV VG Fmt Attr PSize PFree
/dev/sda lvm2 --- 128.00m 128.00m
Also, this problem had not appeared before changes introduced
by commits e1a63905d14cc73352b905c70cb4084b7e521e33 through
3a6f91d7139119bea664050a957cbc21490398bc which, among other
things, added proper label field type reporting. Before, label
reporting was the same as using struct physical_volume which
has its own dev field assigned and so this problem was not exposed.
| -rw-r--r-- | WHATS_NEW | 1 | ||||
| -rw-r--r-- | lib/format_text/format-text.c | 1 |
2 files changed, 2 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.02.132 - ====================================== + Fix PV label processing failure after pvcreate in lvm shell with lvmetad. Version 2.02.131 - 15th September 2015 ====================================== diff --git a/lib/format_text/format-text.c b/lib/format_text/format-text.c index 4544f265e..e0ec8edf1 100644 --- a/lib/format_text/format-text.c +++ b/lib/format_text/format-text.c @@ -1339,6 +1339,7 @@ static int _text_pv_write(const struct format_type *fmt, struct physical_volume label = lvmcache_get_label(info); label->sector = pv->label_sector; + label->dev = pv->dev; lvmcache_update_pv(info, pv, fmt); |