There were a bunch of new reports in the last week. Not sure why,
maybe a bogus tutorial out there or something along those lines.
Thin pools with zeroing during allocation turned off are currently not
supported for VM images. Using such a pool may lead to data
corruption for various operations like drive mirror.
Document this and add a check in the storage plugin upon storage
activation.
In the future, a dedicated storage configuration option could be
introduced that can be checked by volume_has_feature() and enforced
upon storage activation.
docs:
Fiona Ebner (1):
close #7204: storage: lvm thin: document that thin pools must have
zeroing enabled
pve-storage-lvmthin.adoc | 5 +++++
1 file changed, 5 insertions(+)
storage:
Fiona Ebner (2):
lvm plugin: list volumes: also query 'zero' property
close #7204: lvm thin plugin: die if thin pool does not have zeroing
configured
src/PVE/Storage/LVMPlugin.pm | 6 ++++--
src/PVE/Storage/LvmThinPlugin.pm | 17 ++++++++++++++++-
2 files changed, 20 insertions(+), 3 deletions(-)
Summary over all repositories:
3 files changed, 25 insertions(+), 3 deletions(-)
--
Generated by git-murpp 0.5.0
