From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH v3 proxmox-backup 0/9] fix #5982: check atime update is honored
Date: Tue, 4 Mar 2025 19:35:37 +0100 [thread overview]
Message-ID: <20250304183546.461918-1-c.ebner@proxmox.com> (raw)
These patches add a check to phase 1 of garbage collection in order
to detect when the filesystem backing the chunk store does not honor
atime updates. This avoids possible data loss for situations where
garbage collection could otherwise delete chunks still referenced by
a backup snaphost's index file.
The check is performed by inserting a fixed size 4 MiB unencrypted and
compressed chunk of all-zeros. The check is performed by setting the
atime to 1 second in the past followed by setting it to now in order to
test if atime updates are honored immediately. The test is performed
on datastore creation for early detection and before garbage collection
phase 1. The test is enabled by default, but an opt-out option can be
set via the datastore tuning parameters for backwards compatibility.
Further, add a datastore tuning parameter to reduce the wait period for
chunk removal in phase 2 of garbage collection. Make this conditional on
the atime update check being enabled and successful, to avoid possible
data loss.
Most notable changes sice version 1 (thanks Fabian and Thomas for
comments and suggestions):
- Take into account Linux timestamp granularity, do not set timestamp
to the past, as that introduces other error paths such as lack of
permissions or fs limitations.
- Check relatime behavior, if atime behaviour is not honored. Fallback
to original cutoff in that case.
- Adapt tuning parameter names.
Most notable changes sice version 1 (thanks Fabian and Thomas for
comments and suggestions):
- Optimize check by using the all zero chunk
- Enable the check by default and fail GC job if not honored, but allow
to opt-out
- Add GC wait period tuning option
Link to the issue in the bugtracker:
https://bugzilla.proxmox.com/show_bug.cgi?id=5982
proxmox:
Christian Ebner (2):
pbs api types: add garbage collection atime safety check flag
pbs api types: add option to set GC chunk cleanup atime cutoff
pbs-api-types/src/datastore.rs | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
proxmox-backup:
Christian Ebner (7):
datastore: use libc's timespec constants instead of redefinition
fix #5982: garbage collection: check atime updates are honored
ui: expose GC atime safety check flag in datastore tuning options
docs: mention GC atime update check for tuning options
datastore: conditionally use custom GC atime cutoff if set
ui: expose GC atime cutoff in datastore tuning option
docs: mention gc-atime-cutoff as datastore tuning option
docs/storage.rst | 19 +++-
pbs-datastore/src/chunk_store.rs | 144 ++++++++++++++++++++++++++++---
pbs-datastore/src/datastore.rs | 32 +++++++
src/api2/config/datastore.rs | 1 +
www/Utils.js | 9 ++
www/datastore/OptionView.js | 17 ++++
6 files changed, 208 insertions(+), 14 deletions(-)
--
2.39.5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-03-04 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 18:35 Christian Ebner [this message]
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox 1/2] pbs api types: add garbage collection atime safety check flag Christian Ebner
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox 2/2] pbs api types: add option to set GC chunk cleanup atime cutoff Christian Ebner
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 3/9] datastore: use libc's timespec constants instead of redefinition Christian Ebner
2025-03-05 9:41 ` [pbs-devel] applied: " Fabian Grünbichler
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 4/9] fix #5982: garbage collection: check atime updates are honored Christian Ebner
2025-03-05 9:41 ` Fabian Grünbichler
2025-03-05 10:31 ` Christian Ebner
2025-03-05 9:41 ` Fabian Grünbichler
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 5/9] ui: expose GC atime safety check flag in datastore tuning options Christian Ebner
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 6/9] docs: mention GC atime update check for " Christian Ebner
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 7/9] datastore: conditionally use custom GC atime cutoff if set Christian Ebner
2025-03-05 9:41 ` Fabian Grünbichler
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 8/9] ui: expose GC atime cutoff in datastore tuning option Christian Ebner
2025-03-04 18:35 ` [pbs-devel] [PATCH v3 proxmox-backup 9/9] docs: mention gc-atime-cutoff as " Christian Ebner
2025-03-05 9:41 ` [pbs-devel] [PATCH v3 proxmox-backup 0/9] fix #5982: check atime update is honored Fabian Grünbichler
2025-03-05 15:17 ` Christian Ebner
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=20250304183546.461918-1-c.ebner@proxmox.com \
--to=c.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.