From: "Jan Lübbe" <jlu@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Tobias Waldekranz <tobias@waldekranz.com>,
barebox@lists.infradead.org
Cc: Richard Weinberger <richard@nod.at>,
Michael Olbrich <mol@pengutronix.de>,
anis chali <chalianis1@gmail.com>,
Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [PATCH 0/5] dm: Initial work on a device mapper
Date: Tue, 02 Sep 2025 16:34:53 +0200 [thread overview]
Message-ID: <13ed39c286a4dfcccfc3cfa30e987b782a4e800d.camel@pengutronix.de> (raw)
In-Reply-To: <07a7e6e0-f0dd-4969-888a-b616fe337158@pengutronix.de>
On Fri, 2025-08-29 at 13:24 +0200, Ahmad Fatoum wrote:
> > 2. Barebox is a much higher quality code base to work in than
> > U-Boot. I'm sorry, but it just is.
> >
> > Barebox would thus take the place occupied by systemd-boot in many
> > distro setups. So why not go with systemd-boot?
>
> Sidenote: Something that been irking me for ages is the over-reliance
> on FAT in systemd-boot. Could the FAT on a file system level break
> by inopportune power cuts? We go to great lengths with barebox-state
> and redundant buckets on raw partitions to avoid this and it leaves
> me asking: Was I wrong to mistrust FAT or is a sudden power cut during
> file system write operations not as much a concern for their users?
>
> I hope someone (maybe me instead of talking) should do fault injection
> in QEMU or using kernel APIs and see how broken it can get.
For the kernel, there is:
https://docs.kernel.org/admin-guide/device-mapper/log-writes.html
https://github.com/josefbacik/log-writes
Perhaps this could be used via the sandbox build or even QEMU to produce such a
log. Then, you could use the userspace tool to reproduce all intermediate states
and check that they are consistent.
Doing this has been on my wishlist for ages, but I've never gotten around to it.
Also in this area, I've wondered for some time if an alternative implementation
of FAT would be possible which does a strictly ordered commit of a new meta-data
tree on unmount. As there are two copies of the top-level FAT, it might be
possible to do that atomically by using a careful ordering of writes. By now,
FAT is basically only used as a boot partition, so trading performance for
reliability might be a good idea. :)
Regards,
Jan
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-09-02 19:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 15:05 Tobias Waldekranz
2025-08-28 15:05 ` [PATCH 1/5] string: add strtok/strtokv Tobias Waldekranz
2025-08-28 15:05 ` [PATCH 2/5] dm: Add initial device mapper infrastructure Tobias Waldekranz
2025-08-28 15:05 ` [PATCH 3/5] dm: linear: Add linear target Tobias Waldekranz
2025-08-29 5:56 ` Ahmad Fatoum
2025-08-28 15:05 ` [PATCH 4/5] test: self: dm: Add test of " Tobias Waldekranz
2025-08-28 15:05 ` [PATCH 5/5] commands: dmsetup: Basic command set for dm device management Tobias Waldekranz
2025-08-29 8:29 ` [PATCH 0/5] dm: Initial work on a device mapper Sascha Hauer
2025-08-31 7:48 ` Tobias Waldekranz
2025-09-02 8:40 ` Ahmad Fatoum
2025-09-02 9:44 ` Tobias Waldekranz
2025-08-29 11:24 ` Ahmad Fatoum
2025-08-31 7:48 ` Tobias Waldekranz
2025-09-02 9:03 ` Ahmad Fatoum
2025-09-02 13:01 ` Tobias Waldekranz
2025-09-02 14:46 ` Jan Lübbe
2025-09-02 21:34 ` Tobias Waldekranz
2025-09-02 14:34 ` Jan Lübbe [this message]
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=13ed39c286a4dfcccfc3cfa30e987b782a4e800d.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.com \
--cc=m.felsch@pengutronix.de \
--cc=mol@pengutronix.de \
--cc=richard@nod.at \
--cc=tobias@waldekranz.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