diff options
| author | Baokun Li <[email protected]> | 2025-01-22 11:41:29 +0000 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2025-03-13 14:16:34 +0000 |
| commit | 6b76715d5e41fc332b0b879e66fad6ef3db07a3f (patch) | |
| tree | fe5b362b56153d61833f941b75e6bc2634b9e780 /fs/jbd2/commit.c | |
| parent | ext4: correct behavior under errors=remount-ro mode (diff) | |
| download | kernel-6b76715d5e41fc332b0b879e66fad6ef3db07a3f.tar.gz kernel-6b76715d5e41fc332b0b879e66fad6ef3db07a3f.zip | |
ext4: show 'emergency_ro' when EXT4_FLAGS_EMERGENCY_RO is set
After commit d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem
errors") in v6.12-rc1, the 'errors=remount-ro' mode no longer sets
SB_RDONLY on errors, which results in us seeing the filesystem is still
in rw state after errors.
Therefore, after setting EXT4_FLAGS_EMERGENCY_RO, display the emergency_ro
option so that users can query whether the current file system has become
emergency read-only due to errors through commands such as 'mount' or
'cat /proc/fs/ext4/sdx/options'.
Fixes: d3476f3dad4a ("ext4: don't set SB_RDONLY after filesystem errors")
Signed-off-by: Baokun Li <[email protected]>
Reviewed-by: Jan Kara <[email protected]>
Reviewed-by: Zhang Yi <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions