From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsck: Fix incorrect interior node logical start values
Date: Thu, 29 Nov 2012 08:22:53 -0500 [thread overview]
Message-ID: <20121129132253.GB20413@thunk.org> (raw)
In-Reply-To: <50B6F75C.8070903@redhat.com>
On Wed, Nov 28, 2012 at 11:49:16PM -0600, Eric Sandeen wrote:
> >
> > Wow, that was unnecessarily large. Here's a smaller one...
> >
>
> Was that by hand-hackery or did you figure out how to hit
> it at runtime?
Via hand-hackery. The tst_extents command allow you to do things like
this:
% ./build/lib/ext2fs/tst_extents -w /tmp/test_case.img
tst_extents 1.42.6 (21-Sep-2012)
tst_extents: inode <16>
header: magic=f30a entries=3 max=4 depth=1 generation=0
Loaded inode 16
tst_extents: root
extent: lblk 0--83, len 84, pblk 1731, flags: (none)
tst_extents: next_sibling
extent: lblk 84--4021, len 3938, pblk 1899, flags: (none)
tst_extents: replace_node 80 0 1899
extent replace: 16 extent: lblk 80--79, len 0, pblk 1899, flags: (none)
extent: lblk 80--4021, len 3942, pblk 1899, flags: (none)
tst_extents: prev_sibling
extent: lblk 0--79, len 80, pblk 1731, flags: 2ND_VISIT
tst_extents: q
- Ted
next prev parent reply other threads:[~2012-11-29 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 19:47 [PATCH] e2fsck: Fix incorrect interior node logical start values Eric Sandeen
2012-11-16 2:54 ` Andreas Dilger
2012-11-16 3:10 ` Eric Sandeen
[not found] ` <20121129044609.GC8029@thunk.org>
2012-11-29 4:52 ` Theodore Ts'o
2012-11-29 5:49 ` Eric Sandeen
2012-11-29 13:22 ` Theodore Ts'o [this message]
2012-11-29 13:31 ` Theodore Ts'o
2012-11-29 15:22 ` Eric Sandeen
2012-11-29 16:40 ` Theodore Ts'o
2012-11-29 16:43 ` Eric Sandeen
2012-11-29 18:56 ` Eric Sandeen
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=20121129132253.GB20413@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).