]> git.ipfire.org Git - thirdparty/e2fsprogs.git/commit
projects / thirdparty / e2fsprogs.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 26769ab) | patch
e2fsck: use "Optimize?" prompt for PR_1E_CAN_{COLLAPSE,NARROW}_EXTENT_TREE
authorTheodore Ts'o <tytso@mit.edu>
Sun, 16 Dec 2018 03:13:41 +0000 (22:13 -0500)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 16 Dec 2018 03:37:53 +0000 (22:37 -0500)
commitce75cf5459ee130dfe8980a6a16af1947d410ff1
tree3971ef722aacc7e0814d09006c03a99cdeed3c89tree | snapshot
parent26769abf806c9534fb6be296abe94d4c6f296a32commit | diff
e2fsck: use "Optimize?" prompt for PR_1E_CAN_{COLLAPSE,NARROW}_EXTENT_TREE

If e2fsck can optimize an inode's extent tree, it should ask for
permission to optimize it, not to "fix" it.  This was causing some
confusion, since some users interpreted this prompt as an indication
that the file system was inconsistent.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
e2fsck/problem.c diff | blob | blame | history
tests/d_punch/expect diff | blob | blame | history
tests/d_punch_bigalloc/expect diff | blob | blame | history
tests/f_collapse_extent_tree/expect.1 diff | blob | blame | history
tests/f_compress_extent_tree_level/expect.1 diff | blob | blame | history
tests/f_extent_bad_node/expect.1 diff | blob | blame | history
tests/f_extent_int_bad_magic/expect.1 diff | blob | blame | history
tests/f_extent_leaf_bad_magic/expect.1 diff | blob | blame | history
tests/f_extent_oobounds/expect.1 diff | blob | blame | history
tests/f_quota_extent_opt/expect.1 diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.