From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] config: add default datastore creation function
Date: Fri, 3 May 2024 17:31:05 +0200 [thread overview]
Message-ID: <8798da2f-5fb6-4570-9b9b-23e81fee2555@proxmox.com> (raw)
In-Reply-To: <1696409104.14075.1714747792149@webmail.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
next prev parent reply other threads:[~2024-05-03 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 14:29 Gabriel Goller
2024-05-03 14:29 ` [pbs-devel] [PATCH proxmox-backup 2/2] disks: unify default datastore creation Gabriel Goller
2024-05-03 14:32 ` [pbs-devel] [PATCH proxmox-backup 1/2] config: add default datastore creation function Gabriel Goller
2024-05-03 14:49 ` Christian Ebner
2024-05-03 15:31 ` Christian Ebner [this message]
2024-05-13 8:52 ` Christian Ebner
2024-05-13 9:31 ` Gabriel Goller
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=8798da2f-5fb6-4570-9b9b-23e81fee2555@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pbs-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