diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2018-12-15 22:13:41 -0500 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2018-12-15 22:37:53 -0500 |
| commit | ce75cf5459ee130dfe8980a6a16af1947d410ff1 (patch) | |
| tree | 3971ef722aacc7e0814d09006c03a99cdeed3c89 /tests/d_punch | |
| parent | 26769abf806c9534fb6be296abe94d4c6f296a32 (diff) | |
| download | e2fsprogs-ce75cf5459ee130dfe8980a6a16af1947d410ff1.tar.gz | |
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>
Diffstat (limited to 'tests/d_punch')
| -rw-r--r-- | tests/d_punch/expect | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/tests/d_punch/expect b/tests/d_punch/expect index 2b39f8ec..b13462b7 100644 --- a/tests/d_punch/expect +++ b/tests/d_punch/expect @@ -127,37 +127,37 @@ Level Entries Logical Physical Length Flags 0/ 0 1/ 2 0 - 0 9000 - 9000 1 Uninit 0/ 0 2/ 2 8999 - 8999 17999 - 17999 1 Uninit Pass 1: Checking inodes, blocks, and sizes -Inode 15 extent tree (at level 1) could be shorter. Fix? yes +Inode 15 extent tree (at level 1) could be shorter. Optimize? yes -Inode 16 extent tree (at level 1) could be shorter. Fix? yes +Inode 16 extent tree (at level 1) could be shorter. Optimize? yes -Inode 17 extent tree (at level 1) could be shorter. Fix? yes +Inode 17 extent tree (at level 1) could be shorter. Optimize? yes -Inode 18 extent tree (at level 1) could be shorter. Fix? yes +Inode 18 extent tree (at level 1) could be shorter. Optimize? yes -Inode 19 extent tree (at level 1) could be shorter. Fix? yes +Inode 19 extent tree (at level 1) could be shorter. Optimize? yes -Inode 20 extent tree (at level 1) could be shorter. Fix? yes +Inode 20 extent tree (at level 1) could be shorter. Optimize? yes -Inode 21 extent tree (at level 1) could be shorter. Fix? yes +Inode 21 extent tree (at level 1) could be shorter. Optimize? yes -Inode 22 extent tree (at level 1) could be shorter. Fix? yes +Inode 22 extent tree (at level 1) could be shorter. Optimize? yes -Inode 23 extent tree (at level 1) could be shorter. Fix? yes +Inode 23 extent tree (at level 1) could be shorter. Optimize? yes -Inode 24 extent tree (at level 1) could be shorter. Fix? yes +Inode 24 extent tree (at level 1) could be shorter. Optimize? yes -Inode 25 extent tree (at level 1) could be shorter. Fix? yes +Inode 25 extent tree (at level 1) could be shorter. Optimize? yes -Inode 26 extent tree (at level 1) could be shorter. Fix? yes +Inode 26 extent tree (at level 1) could be shorter. Optimize? yes -Inode 27 extent tree (at level 1) could be shorter. Fix? yes +Inode 27 extent tree (at level 1) could be shorter. Optimize? yes -Inode 28 extent tree (at level 1) could be shorter. Fix? yes +Inode 28 extent tree (at level 1) could be shorter. Optimize? yes -Inode 29 extent tree (at level 1) could be shorter. Fix? yes +Inode 29 extent tree (at level 1) could be shorter. Optimize? yes -Inode 30 extent tree (at level 1) could be shorter. Fix? yes +Inode 30 extent tree (at level 1) could be shorter. Optimize? yes Pass 1E: Optimizing extent trees Pass 2: Checking directory structure |