From: Victor Seva via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Victor Seva <linuxmaniac@torreviejawireless.org>
Subject: [pve-devel] [PATCH] fix #957 iscsi: don't check tcp connection directly
Date: Wed, 5 Mar 2025 22:59:37 +0100 [thread overview]
Message-ID: <mailman.800.1741212404.293.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5385 bytes --]
From: Victor Seva <linuxmaniac@torreviejawireless.org>
To: pve-devel@lists.proxmox.com
Subject: [PATCH] fix #957 iscsi: don't check tcp connection directly
Date: Wed, 5 Mar 2025 22:59:37 +0100
Message-ID: <20250305215937.53650-1-linuxmaniac@torreviejawireless.org>
pvestatd is checking this every 10 seconds. This check
produces a lot of noise at the iscsi server logging.
Use iscsiadm command to check the sessions status instead
Signed-off-by: Victor Seva <linuxmaniac@torreviejawireless.org>
---
src/PVE/Storage/ISCSIPlugin.pm | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/src/PVE/Storage/ISCSIPlugin.pm b/src/PVE/Storage/ISCSIPlugin.pm
index eb70453..6a69653 100644
--- a/src/PVE/Storage/ISCSIPlugin.pm
+++ b/src/PVE/Storage/ISCSIPlugin.pm
@@ -66,6 +66,25 @@ sub iscsi_test_portal {
return PVE::Network::tcp_ping($server, $port || 3260, 2);
}
+sub iscsi_test_session {
+ my ($portal, $sid) = @_;
+ my $cmd = [$ISCSIADM, '--mode', 'session', '--sid', $sid, '-P1'];
+
+ my $res = 0;
+ eval {
+ run_command($cmd, errmsg => 'iscsi session test failed', outfunc => sub {
+ my $line = shift;
+ if ($line =~ m/^\s+iSCSI Session State: LOGGED_IN\s*$/) {
+ $res = 1;
+ }
+ });
+ };
+ if (my $err = $@) {
+ die $err;
+ };
+ return $res;
+}
+
sub iscsi_portals {
my ($target, $portal_in) = @_;
@@ -561,10 +580,13 @@ sub check_connection {
my ($class, $storeid, $scfg) = @_;
my $portals = iscsi_portals($scfg->{target}, $scfg->{portal});
-
+ my $cache = {};
for my $portal (@$portals) {
- my $result = iscsi_test_portal($portal);
- return $result if $result;
+ my $sessions = iscsi_session($cache, $scfg->{target});
+ for my $session (@$sessions) {
+ my $result = iscsi_test_session($portal, $session->{session_id});
+ return $result if $result;
+ }
}
return 0;
--
2.43.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-03-05 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 21:59 Victor Seva via pve-devel [this message]
2025-03-07 11:59 ` Mira Limbeck
2025-03-07 12:03 ` Mira Limbeck
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=mailman.800.1741212404.293.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=linuxmaniac@torreviejawireless.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: 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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal