d3d566f7bd
Used chunks are marked in phase1 of the garbage collection process by using the atime property. Each used chunk gets touched so that the atime gets updated (if older than 24h, see relatime). Should there ever be a situation in which the phase1 in the GC run needs a very long time to finish, it could happen that the grace period calculated in phase2 is not long enough and thus the marking of the chunks (atime) becomes invalid. This would result in the removal of needed chunks. Even though the likelyhood of this happening is very low, using the timestamp from right before phase1 is started, to calculate the grace period in phase2 should avoid this situation. Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
``rustup`` Toolchain
====================
We normally want to build with the ``rustc`` Debian package. To do that
you can set the following ``rustup`` configuration:
# rustup toolchain link system /usr
# rustup default system
Versioning of proxmox helper crates
===================================
To use current git master code of the proxmox* helper crates, add::
git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox"
or::
path = "../proxmox/proxmox"
to the proxmox dependency, and update the version to reflect the current,
pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0").
Local cargo config
==================
This repository ships with a ``.cargo/config`` that replaces the crates.io
registry with packaged crates located in ``/usr/share/cargo/registry``.
A similar config is also applied building with dh_cargo. Cargo.lock needs to be
deleted when switching between packaged crates and crates.io, since the
checksums are not compatible.
To reference new dependencies (or updated versions) that are not yet packaged,
the dependency needs to point directly to a path or git source (e.g., see
example for proxmox crate above).