From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Josef Bacik <jbacik@fb.com>,
fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 00/13] Crash consistency xfstest using dm-log-writes
Date: Tue, 5 Sep 2017 22:11:07 +0300 [thread overview]
Message-ID: <1504638680-25682-1-git-send-email-amir73il@gmail.com> (raw)
Eryu,
This is the 3rd revision of crash consistency patch set.
I addressed all your review commennts on v2 patches.
These patches are originally from Josef Bacik.
I've added some debugging options for running fsx
and replay-log, which I used to analyze the crash consistency
bugs uncovered by the tests.
The original fsx crash consistency test (500) is failing sometimes
on kernel v4.13 for ext4, btrfs and xfs.
A fix for xfs is queued for v4.14, I think there is a fix by Josef
for btrfs queued for v4.14 as well.
A 'quick' and reliable regression test (501) was created for the
ext4 issue.
I created another crash consistency test which runs fsx on cloned
files (502). This test is failing check fs sometimes on kernel v4.13,
at the end of the test, but this is not related to crash consistency.
There is a fix is the works for v4.14.
A 'quick' and reliable regression test (503) was created for this issue.
The new 'clones crash' test (502) is also failing sometimes on xfs_repair
errors like: "fatal error -- illegal state 13 in block map 147", on crash
points, but I havn't been able to narrow down the issue yet.
Amir.
Amir Goldstein (13):
fsx: add support for integrity check with dm-log-writes target
fsx: add optional logid prefix to log messages
fsx: add support for recording operations to a file
fsx: add support for writing constant instead of random data
fsx: add support for keeping existing file
log-writes: add replay-log program to replay dm-log-writes target
replay-log: add validations for corrupt log entries
replay-log: add support for replaying ops in target device sector
fstests: add support for working with dm-log-writes target
fstests: crash consistency fsx test using dm-log-writes
fstests: regression test for ext4 crash consistency bug
fstests: crash consistency fsx test for cloned files
fstests: regression test for xfs leftover CoW extent error
.gitignore | 1 +
README | 2 +
common/dmlogwrites | 94 +++++++++
doc/auxiliary-programs.txt | 8 +
doc/requirement-checking.txt | 20 ++
ltp/fsx.c | 246 ++++++++++++++++++-----
src/Makefile | 2 +-
src/log-writes/Makefile | 23 +++
src/log-writes/SOURCE | 6 +
src/log-writes/log-writes.c | 458 +++++++++++++++++++++++++++++++++++++++++++
src/log-writes/log-writes.h | 81 ++++++++
src/log-writes/replay-log.c | 389 ++++++++++++++++++++++++++++++++++++
tests/generic/500 | 135 +++++++++++++
tests/generic/500.out | 2 +
tests/generic/501 | 80 ++++++++
tests/generic/501.out | 2 +
tests/generic/502 | 142 ++++++++++++++
tests/generic/502.out | 2 +
tests/generic/503 | 69 +++++++
tests/generic/503.out | 2 +
tests/generic/group | 4 +
21 files changed, 1721 insertions(+), 47 deletions(-)
create mode 100644 common/dmlogwrites
create mode 100644 src/log-writes/Makefile
create mode 100644 src/log-writes/SOURCE
create mode 100644 src/log-writes/log-writes.c
create mode 100644 src/log-writes/log-writes.h
create mode 100644 src/log-writes/replay-log.c
create mode 100755 tests/generic/500
create mode 100644 tests/generic/500.out
create mode 100755 tests/generic/501
create mode 100644 tests/generic/501.out
create mode 100755 tests/generic/502
create mode 100644 tests/generic/502.out
create mode 100755 tests/generic/503
create mode 100644 tests/generic/503.out
--
2.7.4
next reply other threads:[~2017-09-05 19:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 19:11 Amir Goldstein [this message]
2017-09-05 19:11 ` [PATCH v3 01/13] fsx: add support for integrity check with dm-log-writes target Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 02/13] fsx: add optional logid prefix to log messages Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 03/13] fsx: add support for recording operations to a file Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 04/13] fsx: add support for writing constant instead of random data Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 05/13] fsx: add support for keeping existing file Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 06/13] log-writes: add replay-log program to replay dm-log-writes target Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 07/13] replay-log: add validations for corrupt log entries Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 08/13] replay-log: add support for replaying ops in target device sector range Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 09/13] fstests: add support for working with dm-log-writes target Amir Goldstein
2017-09-07 7:45 ` Eryu Guan
2017-09-07 7:47 ` Eryu Guan
2017-09-05 19:11 ` [PATCH v3 10/13] fstests: crash consistency fsx test using dm-log-writes Amir Goldstein
2017-09-07 7:50 ` Eryu Guan
2017-09-07 8:50 ` Amir Goldstein
2017-09-07 8:55 ` Eryu Guan
2017-09-07 10:10 ` Amir Goldstein
2017-11-27 9:56 ` Amir Goldstein
2017-11-27 14:23 ` Ashlie Martinez
2017-11-27 15:07 ` Josef Bacik
2017-11-27 15:04 ` Josef Bacik
2017-11-28 16:48 ` Amir Goldstein
2017-11-28 17:21 ` Josef Bacik
2017-11-28 19:32 ` Amir Goldstein
2017-11-28 20:00 ` Josef Bacik
2017-11-28 20:26 ` Amir Goldstein
[not found] ` <CAOQ4uxhQu-1AK71zg4Ce0cJd+xRt3Gf9zMMVb=Rs00zFuWA3hQ@mail.gmail.com>
2017-11-28 22:33 ` Darrick J. Wong
2017-11-29 3:33 ` Amir Goldstein
[not found] ` <CAOQ4uxhXWxkre7L7RDvpH8E4cwsHGZzVHKmCpBESfTUZhmQpUg@mail.gmail.com>
[not found] ` <CAOQ4uxjBQ9ZzPe9GKCRYCjNFv3jP8NMAVQDb=LiNqNcEeRp47w@mail.gmail.com>
2017-12-04 20:53 ` Darrick J. Wong
2017-09-05 19:11 ` [PATCH v3 11/13] fstests: regression test for ext4 crash consistency bug Amir Goldstein
2017-09-07 7:52 ` Eryu Guan
2017-09-05 19:11 ` [PATCH v3 12/13] fstests: crash consistency fsx test for cloned files Amir Goldstein
2017-09-05 19:11 ` [PATCH v3 13/13] fstests: regression test for xfs leftover CoW extent error Amir Goldstein
2017-09-07 7:55 ` Eryu Guan
2017-09-07 9:34 ` Amir Goldstein
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=1504638680-25682-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jbacik@fb.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.