diff options
| author | Nikita Ofitserov <himikof@gmail.com> | 2025-07-03 02:59:11 +0300 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2025-07-03 01:20:19 -0400 |
| commit | 9a20220fd3c17af8407b1cf13acc6bcafbce2104 (patch) | |
| tree | d7790f3f26856d0eb28cb026f2d577491bc8fe7e /scripts/bash-completion | |
| parent | c8b5d5a9c85b1e79f5c1ee5d825c2ebded636674 (diff) | |
bcachefs: Suppress unnecessary inode_i_sectors_wrong fsck errorfor-next
It is possible that fsck first miscounted the expected sector count (due
to applying other fixes at the same time, for example) and then
corrected itself using extents. No need to log an fsck error and
write the inode in this case.
Signed-off-by: Nikita Ofitserov <himikof@gmail.com>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'scripts/bash-completion')
0 files changed, 0 insertions, 0 deletions