Whamcloud - gitweb
e2fsck: exit with exit status 0 if no errors were fixed
authorTheodore Ts'o <tytso@mit.edu>
Fri, 17 Feb 2017 03:02:35 +0000 (22:02 -0500)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 17 Feb 2017 03:02:35 +0000 (22:02 -0500)
commitbf9f3b6d5b10d19218b4ed904c12b22e36ec57dd
tree06b3cb37bf2a064dfb5cf0a790572495b1fbd049
parent03a179a10ef44c7057d5aad3d6654ee6b507f2ed
e2fsck: exit with exit status 0 if no errors were fixed

Previously, e2fsck would exit with a status code of 1 even though the
only changes that it made to the file system were various
optimziations and not fixing file system corruption.  Since the man
page states that an exit status of 1 means "file system errors
corrupted", fix e2fsck to return an exit status of 0.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
16 files changed:
e2fsck/e2fsck.conf.5.in
e2fsck/journal.c
e2fsck/problem.c
e2fsck/problemP.h
e2fsck/unix.c
tests/f_collapse_extent_tree/expect.1
tests/f_compress_extent_tree_level/expect.1
tests/f_convert_bmap/expect.1
tests/f_convert_bmap_and_extent/expect.1
tests/f_extent_htree/expect.1
tests/f_jnl_errno/expect.1
tests/f_journal/expect.1
tests/f_orphan/expect.1
tests/f_orphan_extents_inode/expect.1
tests/f_rehash_dir/expect.1
tests/f_unsorted_EAs/expect.1