From: Lukas Czerner <lczerner@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, Lukas Czerner <lczerner@redhat.com>
Subject: [PATCH 2/2] e2fsprogs tests: fix f_bad_disconnected_inode e2fsck output
Date: Wed, 21 Mar 2012 13:34:53 +0100 [thread overview]
Message-ID: <1332333293-25028-2-git-send-email-lczerner@redhat.com> (raw)
In-Reply-To: <1332333293-25028-1-git-send-email-lczerner@redhat.com>
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@redhat.com>
---
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
next prev parent reply other threads:[~2012-03-21 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:34 [PATCH 1/2] e2fsck: remove EXT4_EOFBLOCKS_FL flag handling Lukas Czerner
2012-03-21 12:34 ` Lukas Czerner [this message]
2012-03-23 0:18 ` [PATCH 2/2] e2fsprogs tests: fix f_bad_disconnected_inode e2fsck output Ted Ts'o
2012-03-23 8:03 ` Lukas Czerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1332333293-25028-2-git-send-email-lczerner@redhat.com \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).