From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pbs-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 1C9FC1FF38D
	for <inbox@lore.proxmox.com>; Fri,  3 May 2024 17:31:10 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 7AE3B41D4;
	Fri,  3 May 2024 17:31:11 +0200 (CEST)
Message-ID: <8798da2f-5fb6-4570-9b9b-23e81fee2555@proxmox.com>
Date: Fri, 3 May 2024 17:31:05 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
 <pbs-devel@lists.proxmox.com>, Gabriel Goller <g.goller@proxmox.com>
References: <20240503142933.171798-1-g.goller@proxmox.com>
 <D102ZOO1HHTO.1ABIFQS5IEGR4@proxmox.com>
 <1696409104.14075.1714747792149@webmail.proxmox.com>
Content-Language: en-US, de-DE
In-Reply-To: <1696409104.14075.1714747792149@webmail.proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.028 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 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
 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
 http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
 information. [proxmox.com]
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] config: add default
 datastore creation function
X-BeenThere: pbs-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox Backup Server development discussion
 <pbs-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, 
 <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/>
List-Post: <mailto:pbs-devel@lists.proxmox.com>
List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, 
 <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox Backup Server development discussion
 <pbs-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: pbs-devel-bounces@lists.proxmox.com
Sender: "pbs-devel" <pbs-devel-bounces@lists.proxmox.com>

On 5/3/24 16:49, Christian Ebner wrote:
>> On 03.05.2024 16:32 CEST Gabriel Goller <g.goller@proxmox.com> wrote:
>>
>>   
>> I am sure this has been discussed before, but couldn't find anything on
>> the mailing list: Why don't we create a default verify job?
>>
>> It seems sensible to me to add a default verify job that runs once a
>> week or once a month to every datastore (at least those created through
>> the UI).
> 
> Without having looked at your patches yet, there has been some patches and discussion on this which you can find here https://lists.proxmox.com/pipermail/pbs-devel/2023-November/007342.html

Forgot to answer your question: verify jobs can be very IO intensive and 
the user might even not want to have one, e.g. if data integrity is 
provided by other means. So this is better set up manually.




_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel