On 1/31/24 09:41, Lennart Poettering wrote:
This tanks performance when writing to the device though. There's a
much better approach however: use an automount in between with a very
short timeout (2s or so). This means the mount appears continously
available from application PoV but the backing fs is only mounted for
a brief time around accesses. This allows caching and asynchronous
behaviour to work, but after 2s everything is forced out to disk
anyway and it is guaranteed the superblock of the disk is put back
into a clean state.
systemd supports this natively, for example with a simple
"systemd-mount -A /dev/sda1".
Another possible approach: run "sync -f" every 3 seconds.
The filesystem will still be dirty, but data should be there
for careless users too. But performance will not be ideal.
On the other hand it avoids a problem that your continuous mount/umount
has: read cache is lost as soon as the device is not continuously active,
which is not optimal.
Regards.
--
Roberto Ragusa mail at robertoragusa.it
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
