From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Christian Storm <christian.storm@siemens.com>,
Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [isar-cip-core][RFC][PATCH 00/10] Provide A/B snapshot support for persistent /var
Date: Thu, 30 Jan 2025 17:11:19 +0100 [thread overview]
Message-ID: <ebee2f73-3aea-4b48-b131-b7d17682242e@siemens.com> (raw)
In-Reply-To: <cover.1738229957.git.jan.kiszka@siemens.com>
On 30.01.25 10:39, Jan Kiszka wrote:
> This is a first attempt to provide a pattern and reusable recipes for
> saving and rolling back the persistent data during A/B updates. The
> obvious approach is using a filesystem that supports snapshots and
> linking those to the rootfs revision that is being booted. As first
> implementation, we are using btrfs. While the current implementation is
> built around btrfs, the concept should not. It may even work with
> device mapper snapshots.
>
> That said, the devil is always in the details. And even this "simple",
> btrfs-only implementation took some rounds to find a logic that neither
> piles up obsolete snapshots or deletes them prematurely. Still, careful
> review is highly welcome, specifically of patch 3.
>
> As we are currently having split /var and /home partitions, this does
> not cover anything in home directories. However, this will automatically
> change when [1] is addressed.
>
Forgot to mention some todos (which are related):
- handling of filesystem errors, likely by resetting to factory state
(blank /var)
- enabling factory reset via explicit requests
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-01-30 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 9:39 [isar-cip-core][RFC][PATCH 00/10] Provide A/B snapshot support for persistent /var Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 01/10] initramfs-crypt-hook: Add support for btrfs Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 02/10] initramfs-crypt-hook: Bump revision Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 03/10] initramfs: Add hook for managing /var in A/B fashion Jan Kiszka
2025-01-30 16:10 ` Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 04/10] initramfs-overlay-hook: Optimize variable initialization Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 05/10] initramfs-overlay-hook: Tune the parameter documentation Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 06/10] initramfs-overlay-hook: Add awareness for abvar hook Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 07/10] initramfs-overlay-hook: Bump revision Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 08/10] swupdate: Make var filesystem type configurable for update images Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 09/10] swupdate: Activate abvar initramfs hook when VAR_FS_TYPE is set to btrfs Jan Kiszka
2025-01-30 9:39 ` [isar-cip-core][RFC][PATCH 10/10] Enable A/B snapshot for /var on x86 and qemu-arm64 Jan Kiszka
2025-01-30 14:06 ` MOESSBAUER, Felix
2025-01-30 15:38 ` Jan Kiszka
2025-01-30 16:11 ` Jan Kiszka [this message]
2025-02-03 17:17 ` [isar-cip-core][RFC][PATCH 00/10] Provide A/B snapshot support for persistent /var Jan Kiszka
2025-02-03 17:29 ` Jan Kiszka
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=ebee2f73-3aea-4b48-b131-b7d17682242e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=christian.storm@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=quirin.gylstorff@siemens.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