From: Ted Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@whamcloud.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2] tests: add two more tests of orphaned inode handling
Date: Wed, 13 Jun 2012 09:26:57 -0400 [thread overview]
Message-ID: <20120613132657.GA12595@thunk.org> (raw)
In-Reply-To: <F7262E20-BC8F-42BE-A8F0-C7DBD49CA8C6@whamcloud.com>
On Wed, Jun 13, 2012 at 12:44:10AM -0600, Andreas Dilger wrote:
> > diff --git a/tests/f_orphan_indirect_inode/expect.1 b/tests/f_orphan_indirect_inode/expect.1
> > new file mode 100644
> > index 0000000..33cdd65
> > --- /dev/null
> > +++ b/tests/f_orphan_indirect_inode/expect.1
> > @@ -0,0 +1,2 @@
> > +test_filesys: clean, 12/16 files, 21/100 blocks
> > +Exit status is 0
>
> Hmm, this doesn't appear to be truncating an orphan inode, unlike
> the f_orphan_extent_inode test is doing?
That's because we're running the test in preen mode, where messages
about the orphan inode processing are suppressed. The bug that this
test is specifically testing for only happens we don't do a full file
system check, and normally tests run with -fy, which forces a full
check.
I overrode the default options used for the first fs check in this
test to be -p. I probably should have used -y instead, so that the
orpan inode message didn't get hidden. I'll fix that for the next
release.
In any case, if you take the image from this test, and run "e2fsck -y
/tmp/image; e2fsck -fy /tmp/image" using the e2fsck from 1.42.3, it'll
become obvious what this test is checking....
- Ted
prev parent reply other threads:[~2012-06-13 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:22 [PATCH] e2fsck: update global free blocks/inodes count when truncating orphan inodes Theodore Ts'o
2012-06-12 5:45 ` [PATCH 1/2] libext2fs: fix block iterator for extents when truncating inodes Theodore Ts'o
2012-06-12 5:45 ` [PATCH 2/2] tests: add two more tests of orphaned inode handling Theodore Ts'o
2012-06-13 6:44 ` Andreas Dilger
2012-06-13 13:26 ` Ted Ts'o [this message]
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=20120613132657.GA12595@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@whamcloud.com \
--cc=linux-ext4@vger.kernel.org \
/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).