On Di, 14.10.25 11:14, Chris Murphy ([email protected]) wrote: > Lack of journal replay support for a small read only driver isn't > brokenness. If the use case requires the journal to be flushed, then > it's expected that use case will use FIFREEZE/FITHAW.
Ahem. Can we please get that FIFREEZE/FITHAW idea out of everybody's head? The fact that on some file systems it flushes the journal is an implementation detail, not a general feature of the concept. You cannot rely on this. Moreover, it does a lot you really *don't* want, i.e. frickin freeze IO on that fs! If that fs is necessary for operation you risk a hung system. It's like eating a rotten egg, just so it cannot spill and get all over your clothes. I mean, sure your clothes might not have gotten dirty, but the fact you are now sick is probably a lot worse. Lennart -- Lennart Poettering, Berlin -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
