Since we removed EOFBLOCKS_FL flag handling, we have to fix the f_bad_disconnected_inode test so that e2fsck output correspond with the new version of the code where we do not check for the EOFBLOCKS_FL flag at all. Simply remove EOFBLOCKS_FL flag warnings from expect.1 e2fsck output. Signed-off-by: Lukas Czerner <lczerner@xxxxxxxxxx> --- tests/f_bad_disconnected_inode/expect.1 | 9 --------- 1 files changed, 0 insertions(+), 9 deletions(-) diff --git a/tests/f_bad_disconnected_inode/expect.1 b/tests/f_bad_disconnected_inode/expect.1 index d3920e3..11862f6 100644 --- a/tests/f_bad_disconnected_inode/expect.1 +++ b/tests/f_bad_disconnected_inode/expect.1 @@ -2,21 +2,12 @@ Pass 1: Checking inodes, blocks, and sizes Inode 1 has EXTENTS_FL flag set on filesystem without extents support. Clear? yes -Inode 9 should not have EOFBLOCKS_FL set (size 0, lblk -1) -Clear? yes - -Inode 10 should not have EOFBLOCKS_FL set (size 0, lblk -1) -Clear? yes - Inode 15 has EXTENTS_FL flag set on filesystem without extents support. Clear? yes Inode 16 has EXTENTS_FL flag set on filesystem without extents support. Clear? yes -Inode 13 should not have EOFBLOCKS_FL set (size 0, lblk -1) -Clear? yes - Pass 2: Checking directory structure Pass 3: Checking directory connectivity /lost+found not found. Create? yes -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
