Feature or enhancement request details
At present our EXT4 library does not support creating a journal and setting a journal mode.
If a user runs a container once and deletes it, a journal likely isn't needed.
For long lived containers that are restarted due to container system stop/start, container crashes, logout/login, and host reboots, the lack of a journal increases the risk of filesystem inconsistency on stop, which can lead to filesystem corruption and latent container crashes/freezes.
The EXT4.Formatter init() function should be enhanced to accept a journal parameter of type JournalConfig?. The JournalConfig type specifies the journal mode and size.
As there is risk to any filesystem change, the default parameter value for journal is nil, which specifies the current no-journal behavior. The implementation should separate the journal setup to minimize the chance of regression in the default case.
Reference: https://www.kernel.org/doc/html/latest/filesystems/ext4/journal.html
Code of Conduct
Feature or enhancement request details
At present our EXT4 library does not support creating a journal and setting a journal mode.
If a user runs a container once and deletes it, a journal likely isn't needed.
For long lived containers that are restarted due to container system stop/start, container crashes, logout/login, and host reboots, the lack of a journal increases the risk of filesystem inconsistency on stop, which can lead to filesystem corruption and latent container crashes/freezes.
The EXT4.Formatter init() function should be enhanced to accept a
journalparameter of typeJournalConfig?. TheJournalConfigtype specifies the journal mode and size.As there is risk to any filesystem change, the default parameter value for
journalisnil, which specifies the current no-journal behavior. The implementation should separate the journal setup to minimize the chance of regression in the default case.Reference: https://www.kernel.org/doc/html/latest/filesystems/ext4/journal.html
Code of Conduct