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 DDC48909AA for ; Thu, 9 Mar 2023 09:59:33 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BF5D5821A for ; Thu, 9 Mar 2023 09:59:03 +0100 (CET) Received: from mail.corep.it (mail.corep.it [93.186.252.128]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Thu, 9 Mar 2023 09:59:03 +0100 (CET) Message-ID: <7ab47597-6ed5-f577-49b5-c011b67ad1a8@corep.it> Date: Thu, 9 Mar 2023 09:52:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 To: pbs-devel@lists.proxmox.com From: dea Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.359 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] Possible problem on NFS storage with release 2-3-3 (??) X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2023 08:59:33 -0000 Hello everyone, I've been using PBS on NFS storage (on several installations) for some time now, and I'm used to some kind of performance. For example, a full SSD datastore (on the NFS datastore) I know takes 2 hours for a full garbage collect, etc. (datastore from 25 to 300 Tbytes). This was always the case until release 2.3-2. After the upgrade to 2.3-3 something changed (ok also to kernel 5.15-85) the same datastore that used to be completed in 2 hours, now after 3 days is 95% in marked mode. Something does not add up for me (datastore side has not been touched a comma), ditto for PBS configuration. The PBS is in production, as soon as I can I would like to upgrade it to kernel 6.1 .... I don't know what could be the cause. I don't understand..... Many thanks Luca