diff options
| author | Jan Kara <jack@suse.cz> | 2020-02-13 11:15:56 +0100 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2020-03-20 11:43:12 -0400 |
| commit | 125850eb92f042c76b6f001bf63833ffc15e7916 (patch) | |
| tree | c68472affceecc6a425a41391611a990ad55ca31 /e2fsck/problem.h | |
| parent | b3f9df9f1ba5ded7031566c94a7a9dfdcbd38aa6 (diff) | |
| download | e2fsprogs-125850eb92f042c76b6f001bf63833ffc15e7916.tar.gz | |
e2fsck: clarify overflow link count error message
When directory link count is set to overflow value (1) but during pass 4
we find out the exact link count would fit, we either silently fix this
(which is not great because e2fsck then reports the fs was modified but
output doesn't indicate why in any way), or we report that link count is
wrong and ask whether we should fix it (in case -n option was
specified). The second case is even more misleading because it suggests
non-trivial fs corruption which then gets silently fixed on the next
run. Similarly to how we fix up other non-problems, just create a new
error message for the case directory link count is not overflown anymore
and always report it to clarify what is going on.
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit 4ebce13292f54c96f43dcb1bd1d5b8df5dc8749d)
Diffstat (limited to 'e2fsck/problem.h')
| -rw-r--r-- | e2fsck/problem.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/e2fsck/problem.h b/e2fsck/problem.h index 5cc89249..7a7294dc 100644 --- a/e2fsck/problem.h +++ b/e2fsck/problem.h @@ -1153,6 +1153,9 @@ struct problem_context { /* directory exceeds max links, but no DIR_NLINK feature in superblock */ #define PR_4_DIR_NLINK_FEATURE 0x040006 +/* Directory ref count set to overflow but it doesn't have to be */ +#define PR_4_DIR_OVERFLOW_REF_COUNT 0x040007 + /* * Pass 5 errors */ |