From: Theodore Ts'o <tytso@mit.edu>
To: Ashlie Martinez <ashmrtn@utexas.edu>
Cc: Amir Goldstein <amir73il@gmail.com>,
Vijay Chidambaram <vvijay03@gmail.com>,
Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: ext4 fix for interaction between i_size, fallocate, and delalloc after a crash
Date: Thu, 30 Nov 2017 09:22:19 -0500 [thread overview]
Message-ID: <20171130142219.qeh3a7hleyvxkmkf@thunk.org> (raw)
In-Reply-To: <20171130044649.xfgwhd2wzdc5mwql@thunk.org>
On Wed, Nov 29, 2017 at 11:46:49PM -0500, Theodore Ts'o wrote:
>
> Can you send the block I/O trace that was observed when you did the
> following, a complete output of dumpe2fs on the file system, and a
> debugfs stat output on the test file?
Oh, and the block I/O trace after CrashMonkey reordered the I/O
operations after the last CACHE FLUSH / barrier operation? I'm
***really*** curious what I/O operations happened *after* the last
barrier operation if you had waited 120 secounds before triggering the
crash.
- Ted
next prev parent reply other threads:[~2017-11-30 14:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 15:43 ext4 fix for interaction between i_size, fallocate, and delalloc after a crash Ashlie Martinez
2017-11-21 16:17 ` Ashlie Martinez
2017-11-22 18:03 ` Theodore Ts'o
2017-11-23 5:39 ` Amir Goldstein
2017-11-27 14:31 ` Ashlie Martinez
2017-11-27 16:11 ` Theodore Ts'o
2017-11-28 13:04 ` Ashlie Martinez
2017-11-28 20:45 ` Theodore Ts'o
2017-11-28 21:27 ` Ashlie Martinez
2017-11-29 3:37 ` Amir Goldstein
2017-11-29 6:13 ` Theodore Ts'o
2017-11-29 8:07 ` Amir Goldstein
2017-11-29 19:58 ` Ashlie Martinez
2017-11-30 0:48 ` Theodore Ts'o
2017-11-30 1:46 ` Ashlie Martinez
2017-11-30 4:46 ` Theodore Ts'o
2017-11-30 14:22 ` Theodore Ts'o [this message]
2017-11-30 14:51 ` Ashlie Martinez
2017-11-30 15:27 ` Theodore Ts'o
2017-11-30 15:40 ` Ashlie Martinez
2017-12-02 20:00 ` Ashlie Martinez
2017-11-30 0:24 ` Theodore Ts'o
2017-11-30 6:46 ` 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=20171130142219.qeh3a7hleyvxkmkf@thunk.org \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=ashmrtn@utexas.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=vvijay03@gmail.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