public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW tools/pvremove.c Date: Mon, 28 Feb 2011 19:35:00 -0000 [thread overview] Message-ID: <20110228193510.7398.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2011-02-28 19:35:10 Modified files: . : WHATS_NEW tools : pvremove.c Log message: Improve pvremove error message when PV belongs to a VG. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1929&r2=1.1930 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/pvremove.c.diff?cvsroot=lvm2&r1=1.32&r2=1.33 --- LVM2/WHATS_NEW 2011/02/28 13:19:02 1.1929 +++ LVM2/WHATS_NEW 2011/02/28 19:35:09 1.1930 @@ -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. --- LVM2/tools/pvremove.c 2011/02/21 12:16:00 1.32 +++ LVM2/tools/pvremove.c 2011/02/28 19:35:10 1.33 @@ -64,8 +64,8 @@ /* 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; }
next reply other threads:[~2011-02-28 19:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-28 19:35 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2006-12-13 18:40 agk 2006-11-17 2:45 agk 2006-04-05 22:24 agk
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20110228193510.7398.qmail@sourceware.org \ --to=agk@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).