When converting to the new liblvm functions, the vgcreate code path
changed to create a new vg, then set values. As a result of this
change, and the fact that we give a user a message if they try to
set the same value of a VG attribute (extent_size, alloc_policy, etc),
you'll see these 2 extraneous "is already" messages with vgcreate:
tools/lvm vgcreate vg2 /dev/loop2
Physical extent size of VG vg2 is already 4.00 MB
Volume group allocation policy is already normal
Volume group "vg2" successfully created
Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
Author: Dave Wysochanski <dwysocha@redhat.com>
Version 2.02.50 -
================================
+ Remove unnecessary messages after vgcreate/vgsplit refactor (2.02.49).
Add log_errno to set a specific errno and replace log_error in due course.
Add lvm_errno and lvm_errmsg to liblvm to obtain failure information.
Change create_toolcontext to still return an object if it fails part-way.
}
if (new_size == vg->extent_size) {
- log_error("Physical extent size of VG %s is already %s",
+ log_verbose("Physical extent size of VG %s is already %s",
vg->name, display_size(vg->cmd, (uint64_t) new_size));
return 1;
}
}
if (alloc == vg->alloc) {
- log_print("Volume group allocation policy is already %s",
+ log_verbose("Volume group allocation policy is already %s",
get_alloc_string(vg->alloc));
return 1;
}