From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E6CA26A1AB for ; Thu, 25 Feb 2021 22:23:39 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D848B8FA1 for ; Thu, 25 Feb 2021 22:23:39 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id C82848F80 for ; Thu, 25 Feb 2021 22:23:38 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 93D094633E for ; Thu, 25 Feb 2021 22:23:38 +0100 (CET) From: Stoiko Ivanov To: pve-devel@lists.proxmox.com Date: Thu, 25 Feb 2021 22:23:05 +0100 Message-Id: <20210225212305.17954-3-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210225212305.17954-1-s.ivanov@proxmox.com> References: <20210225212305.17954-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.064 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH manager 1/1] ui: zpool status detail: add default for scrub information X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 21:23:39 -0000 in case a zpool has not been yet scrubbed, there is no 'scan' information in `zpool status` output. Adding a informational text in that case might help users to notice that something is not configured optimally (e.g. disabled cronjob) Signed-off-by: Stoiko Ivanov --- www/manager6/node/ZFS.js | 1 + 1 file changed, 1 insertion(+) diff --git a/www/manager6/node/ZFS.js b/www/manager6/node/ZFS.js index b54fb4e7..749d7c9b 100644 --- a/www/manager6/node/ZFS.js +++ b/www/manager6/node/ZFS.js @@ -294,6 +294,7 @@ Ext.define('PVE.node.ZFSStatus', { me.rows = { scan: { header: gettext('Scan'), + defaultValue: gettext('No information available (Pool has not been scrubbed yet?)'), }, status: { header: gettext('Status'), -- 2.20.1