From: Ted Ts'o <tytso@mit.edu>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>
Subject: Re: [PATCH 1/5 bigalloc] e2fsprogs: add tool e2wreck to corrupt fs for e2fsck testing
Date: Fri, 18 Nov 2011 22:31:44 -0500 [thread overview]
Message-ID: <20111119033144.GD4130@thunk.org> (raw)
In-Reply-To: <1321613730-10600-2-git-send-email-hao.bigrat@gmail.com>
On Fri, Nov 18, 2011 at 06:55:26PM +0800, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.com>
>
> We need a tool to wreck filesystem to test e2fsck
>
> Signed-off-by: Robin Dong <sanbai@taobao.com>
I don't understand why you need this tool. Debugfs is a more general
tool that will do pretty much everything your proposed e2wreck tool
will do.
The one exception to this is low-level extent tree modifications ---
that functionality is there in the tst_extent program, which is a
debugging program I used when developing the extent support for
e2fsck. Go to the lib/ext2fs directory, and run "make tst_extents".
It's been on my todo list to get a more cleaner support for low-level
extent manipulation to debugfs, but I haven't gotten around to it,
since tst_extents is a serviceable enough, if hacky, substitute.
- Ted
next prev parent reply other threads:[~2011-11-19 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 10:55 [PATCH 0/5 bigalloc] e2fsprogs: change unit of extent's ee_block and ee_len from block to cluster for bigalloc Robin Dong
2011-11-18 10:55 ` [PATCH 1/5 bigalloc] e2fsprogs: add tool e2wreck to corrupt fs for e2fsck testing Robin Dong
2011-11-19 3:31 ` Ted Ts'o [this message]
2011-11-18 10:55 ` [PATCH 2/5 bigalloc] debugfs: support cluster unit of ee_block and ee_len Robin Dong
2011-11-18 10:55 ` [PATCH 3/5 bigalloc] e2fsprogs: make ext2fs_mkdir to support cluster unit of directory Robin Dong
2011-11-18 10:55 ` [PATCH 4/5 bigalloc] e2fsck: support cluster unit of ee_block and ee_len Robin Dong
2011-11-18 10:55 ` [PATCH 5/5 bigalloc] e2fsprogs: make ext2fs_extent_set_bmap() to " Robin Dong
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=20111119033144.GD4130@thunk.org \
--to=tytso@mit.edu \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sanbai@taobao.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).