summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2020-02-13 11:15:56 +0100
committerTheodore Ts'o <tytso@mit.edu>2020-03-07 13:49:43 -0500
commit4ebce13292f54c96f43dcb1bd1d5b8df5dc8749d (patch)
treec39563ec0b60f8299441d619591e92898f47146e /tests
parentb84a5568c7421f494ecd9fe474df6754004df05c (diff)
downloade2fsprogs-4ebce13292f54c96f43dcb1bd1d5b8df5dc8749d.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>
Diffstat (limited to 'tests')
-rw-r--r--tests/f_many_subdirs/expect.12
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/f_many_subdirs/expect.1 b/tests/f_many_subdirs/expect.1
index f2fd78f7..a8da4807 100644
--- a/tests/f_many_subdirs/expect.1
+++ b/tests/f_many_subdirs/expect.1
@@ -17,6 +17,8 @@ Fix? yes
Inode 32963 ref count is 65000, should be 2. Fix? yes
+Directory inode 39601 ref count set to overflow but could be exact value 2. Fix? yes
+
Pass 5: Checking group summary information
Block bitmap differences: -73383
Fix? yes