From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH 2/5] btrfs-progs: Move btrfs-image dump to corresponding dir
Date: Thu, 25 Dec 2014 09:32:12 +0800 [thread overview]
Message-ID: <1419471135-10878-3-git-send-email-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <1419471135-10878-1-git-send-email-quwenruo@cn.fujitsu.com>
Move these obvious btrfs-image to its corresponding dir to use the new
infrastructure.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
.../default_case.img} | Bin
10 files changed, 0 insertions(+), 0 deletions(-)
rename tests/fsck-tests/{001-bad-file-extent-bytenr.img => 001-bad-file-extent-bytenr/default_case.img} (100%)
rename tests/fsck-tests/{002-bad-transid.img => 002-bad-transid/default_case.img} (100%)
rename tests/fsck-tests/{003-shift-offsets.img => 003-shift-offsets/default_case.img} (100%)
rename tests/fsck-tests/{004-no-dir-index.img => 004-no-dir-index/default_case.img} (100%)
rename tests/fsck-tests/{005-bad-item-offset.img => 005-bad-item-offset/default_case.img} (100%)
rename tests/fsck-tests/{008-bad-offset-snapshots.img => 007-bad-offset-snapshots/default_case.img} (100%)
rename tests/fsck-tests/{009-bad-dir-index-name.img => 008-bad-dir-index-name/default_case.img} (100%)
rename tests/fsck-tests/{010-no-dir-item-or-index.img => 009-no-dir-item-or-index/default_case.img} (100%)
rename tests/fsck-tests/{011-no-rootdir-inode-item.img => 010-no-rootdir-inode-item/default_case.img} (100%)
rename tests/fsck-tests/{012-no-inode-item.img => 011-no-inode-item/default_case.img} (100%)
diff --git a/tests/fsck-tests/001-bad-file-extent-bytenr.img b/tests/fsck-tests/001-bad-file-extent-bytenr/default_case.img
similarity index 100%
rename from tests/fsck-tests/001-bad-file-extent-bytenr.img
rename to tests/fsck-tests/001-bad-file-extent-bytenr/default_case.img
diff --git a/tests/fsck-tests/002-bad-transid.img b/tests/fsck-tests/002-bad-transid/default_case.img
similarity index 100%
rename from tests/fsck-tests/002-bad-transid.img
rename to tests/fsck-tests/002-bad-transid/default_case.img
diff --git a/tests/fsck-tests/003-shift-offsets.img b/tests/fsck-tests/003-shift-offsets/default_case.img
similarity index 100%
rename from tests/fsck-tests/003-shift-offsets.img
rename to tests/fsck-tests/003-shift-offsets/default_case.img
diff --git a/tests/fsck-tests/004-no-dir-index.img b/tests/fsck-tests/004-no-dir-index/default_case.img
similarity index 100%
rename from tests/fsck-tests/004-no-dir-index.img
rename to tests/fsck-tests/004-no-dir-index/default_case.img
diff --git a/tests/fsck-tests/005-bad-item-offset.img b/tests/fsck-tests/005-bad-item-offset/default_case.img
similarity index 100%
rename from tests/fsck-tests/005-bad-item-offset.img
rename to tests/fsck-tests/005-bad-item-offset/default_case.img
diff --git a/tests/fsck-tests/008-bad-offset-snapshots.img b/tests/fsck-tests/007-bad-offset-snapshots/default_case.img
similarity index 100%
rename from tests/fsck-tests/008-bad-offset-snapshots.img
rename to tests/fsck-tests/007-bad-offset-snapshots/default_case.img
diff --git a/tests/fsck-tests/009-bad-dir-index-name.img b/tests/fsck-tests/008-bad-dir-index-name/default_case.img
similarity index 100%
rename from tests/fsck-tests/009-bad-dir-index-name.img
rename to tests/fsck-tests/008-bad-dir-index-name/default_case.img
diff --git a/tests/fsck-tests/010-no-dir-item-or-index.img b/tests/fsck-tests/009-no-dir-item-or-index/default_case.img
similarity index 100%
rename from tests/fsck-tests/010-no-dir-item-or-index.img
rename to tests/fsck-tests/009-no-dir-item-or-index/default_case.img
diff --git a/tests/fsck-tests/011-no-rootdir-inode-item.img b/tests/fsck-tests/010-no-rootdir-inode-item/default_case.img
similarity index 100%
rename from tests/fsck-tests/011-no-rootdir-inode-item.img
rename to tests/fsck-tests/010-no-rootdir-inode-item/default_case.img
diff --git a/tests/fsck-tests/012-no-inode-item.img b/tests/fsck-tests/011-no-inode-item/default_case.img
similarity index 100%
rename from tests/fsck-tests/012-no-inode-item.img
rename to tests/fsck-tests/011-no-inode-item/default_case.img
--
2.2.1
next prev parent reply other threads:[~2014-12-25 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 1:32 [PATCH 0/5] New btrfsck test framework Qu Wenruo
2014-12-25 1:32 ` [PATCH 1/5] btrfs-progs: New btrfsck test infrastructure Qu Wenruo
2014-12-25 1:32 ` Qu Wenruo [this message]
2014-12-25 1:32 ` [PATCH 3/5] btrfs-progs: Move bad root items test cases to its corresponding dir Qu Wenruo
2014-12-25 1:32 ` [PATCH 4/5] btrfs-progs: Move leaf-corruption no extent data case and add verification script Qu Wenruo
2014-12-25 1:32 ` [PATCH 5/5] btrfs-progs: Move extent tree rebuild test to its dir Qu Wenruo
2015-01-14 17:25 ` [PATCH 1/2] btrfs-progs: tests, add support for running commands under root David Sterba
2015-01-15 0:33 ` Qu Wenruo
2015-01-19 18:07 ` David Sterba
2015-01-14 17:25 ` [PATCH 2/2] btrfs-progs: teests, use the root helper in 012 David Sterba
2015-01-14 17:43 ` [PATCH 0/5] New btrfsck test framework David Sterba
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=1419471135-10878-3-git-send-email-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@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).