Improve pvremove error message when PV belongs to a VG.

diff --git a/WHATS_NEW b/WHATS_NEW
index 3f228e5b53bd9241415797c40ff30f005dd76ba9..b4e6b369272e76264540f38a55e623b1adadbf92 100644 (file)
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
 Version 2.02.85 - 
 ===================================
+  Improve pvremove error message when PV belongs to a VG.
   Extend normal policy to allow mirror logs on same PVs as images if necessary.
   Improve cling policy to recognise PVs already used during the transaction.
   Improve normal allocation algorithm to include clinging to existing areas.

diff --git a/tools/pvremove.c b/tools/pvremove.c
index ace3c1d00638d8e614bf1ecde1f457906770c407..36da62da2fd94418177340e6e7c98aaa3108c98f 100644 (file)
--- a/tools/pvremove.c
+++ b/tools/pvremove.c
@@ -64,8 +64,8 @@ static int pvremove_check(struct cmd_context *cmd, const char *name)
        /* Allow partial & exported VGs to be destroyed. */
        /* we must have -ff to overwrite a non orphan */
        if (arg_count(cmd, force_ARG) < 2) {
-               log_error("Can't pvremove physical volume \"%s\" of "
-                         "volume group \"%s\" without -ff", name, pv_vg_name(pv));
+               log_error("PV %s belongs to Volume Group %s so please use vgreduce first.", name, pv_vg_name(pv));
+               log_error("(If you are certain you need pvremove, then confirm by using --force twice.)");
                return 0;
        }