From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/2] pve8to9: lvm: use consistent spelling for autoactivation
Date: Mon, 28 Jul 2025 17:10:48 +0200 [thread overview]
Message-ID: <20250728152400.972595-1-f.weber@proxmox.com> (raw)
In some cases, autoactivation was spelled as "auto-activation". Remove
the dash for consistency with other occurrences and the LVM
documentation.
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
PVE/CLI/pve8to9.pm | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm
index fec89a7c..a6ea3f82 100644
--- a/PVE/CLI/pve8to9.pm
+++ b/PVE/CLI/pve8to9.pm
@@ -1631,11 +1631,11 @@ sub check_lvm_autoactivation {
my $autoactivated_guest_lvs =
query_autoactivated_lvm_guest_volumes($cfg, $storeid, $vgname);
if (scalar(@$autoactivated_guest_lvs) > 0) {
- log_notice("storage '$storeid' has guest volumes with auto-activation enabled");
+ log_notice("storage '$storeid' has guest volumes with autoactivation enabled");
$needs_fix = 1;
$shared_affected = 1 if $info->{shared};
} else {
- log_pass("all guest volumes on storage '$storeid' have auto-activation disabled");
+ log_pass("all guest volumes on storage '$storeid' have autoactivation disabled");
}
}
if ($needs_fix) {
@@ -1644,13 +1644,13 @@ sub check_lvm_autoactivation {
my $extra =
$shared_affected
? "Some affected volumes are on shared LVM storages, which has known issues (Bugzilla"
- . " #4997). Disabling auto-activation for those is strongly recommended!"
- : "All volumes with auto-activations reside on local storage, where this normally does"
+ . " #4997). Disabling autoactivation for those is strongly recommended!"
+ : "All volumes with autoactivations reside on local storage, where this normally does"
. " not causes any issues.";
$_log->(
- "Starting with PVE 9, auto-activation will be disabled for new LVM/LVM-thin guest"
- . " volumes. This system has some volumes that still have auto-activation enabled. "
- . "$extra\nYou can run the following command to disable auto-activation for existing"
+ "Starting with PVE 9, autoactivation will be disabled for new LVM/LVM-thin guest"
+ . " volumes. This system has some volumes that still have autoactivation enabled. "
+ . "$extra\nYou can run the following command to disable autoactivation for existing"
. "LVM/LVM-thin "
. "guest volumes:" . "\n\n"
. "\t/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation"
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-28 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:10 Friedrich Weber [this message]
2025-07-28 15:10 ` [pve-devel] [PATCH manager 2/2] pve8to9: lvm: fix missing space and remove unnecessary line break Friedrich Weber
2025-07-29 6:00 ` [pve-devel] applied: [PATCH manager 1/2] pve8to9: lvm: use consistent spelling for autoactivation Thomas Lamprecht
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=20250728152400.972595-1-f.weber@proxmox.com \
--to=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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: link
Be 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