summaryrefslogtreecommitdiff
path: root/udev/69-dm-lvm-metad.rules.in
diff options
context:
space:
mode:
authorAlasdair G Kergon <agk@redhat.com>2014-01-14 03:27:45 +0000
committerAlasdair G Kergon <agk@redhat.com>2014-01-14 03:27:45 +0000
commit3813cd7a3c3e763c346405664fba97edf7110d13 (patch)
treefe509f82e1df1a56d2afb0e1eee7694f56d797e4 /udev/69-dm-lvm-metad.rules.in
parent5a450eab6a9fef7793066864ff58857d827b903f (diff)
downloadlvm2-3813cd7a3c3e763c346405664fba97edf7110d13.tar.gz
format1: Mark obsolete and do not use with lvmetad.
DO NOT USE LVMETAD IF YOU HAVE ANY LVM1-FORMATTED PVS. You may continue to use it without lvmetad, but do please schedule an upgrade to the lvm2 format (with 'vgconvert'). Sending the original LVM1 formatted metadata to lvmetad is breaking assumptions made by the code, so I am marking the format as obsolete for now and no longer sending it to lvmetad. This means that if you are using lvmetad, lvm1 volumes will usually appear invisible - though not always: it depends on exactly what sequence of commands you run! The current situation is not satisfactory. We'll either fix lvmetad and reenable this or we'll fix the code to issue appropriate warning messages when lvm1 PVs are encountered to avoid accidents. (The latest unfixed problem is that lvmetad assumes metadata sequence numbers exist and always increase - but the lvm1 format does not define or store any sequence number, confusing both the daemon and client when default values get passed to-and-fro.)
Diffstat (limited to 'udev/69-dm-lvm-metad.rules.in')
0 files changed, 0 insertions, 0 deletions