From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Theodore Ts'o <tytso@mit.edu>, Dave Jones <davej@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: torrent hash failures since 3.9.0-rc1
Date: Tue, 12 Mar 2013 00:12:27 +0100 [thread overview]
Message-ID: <20130311231227.GA319@x4> (raw)
In-Reply-To: <20130311213837.GA438@x4>
On 2013.03.11 at 22:38 +0100, Markus Trippelsdorf wrote:
> On 2013.03.11 at 17:18 -0400, Theodore Ts'o wrote:
> > On Mon, Mar 11, 2013 at 09:46:25PM +0100, Markus Trippelsdorf wrote:
> > > > BTW, I'm currently running 3.9-rc2 with some additional fixes from the
> > > > ext4 dev branch, and I'm not able to reproduce the problem using
> > > > rtorrent on my laptop. How reliably is it reproducing for you? Are
> > > > you seeing the problem every time you try this?
> > >
> > > Yes, it's 100% reproducible for me. If I boot a 3.8 kernel the issue
> > > vanishes.
> >
> > Would you be willing to try an experiment?
> >
> > Try pulling down the master branch from the ext4 git tree here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> >
> > This contains all of the ext4 changes which are in 3.9-rc1, based on
> > top of 3.8-rc3. See if it reproduces there. If it does, then it
> > would tend to confirm the hypothesis that the issue was introduced by
> > one of the ext4 patches that we merged during the 3.9-rc1 merge
> > window... and then, since if you can reproduce the problem, if you
> > could do a git bisect to find the guilty commit, that would really
> > greatly appreciated.
> >
> > If you can't reproduce it from the ext4.git tree, then the problem is
> > probably caused by some other change that was introduced between 3.8
> > and 3.9-rc1.
>
> I've started a full bisection from v3.8 to todays git tree. It will take
> ~13 steps. However it's already late here in Germany. I will continue
> the bisection tomorrow and report back.
The issue started with:
74cd15cd02708c7188581f279f33a98b2ae8d322 is the first bad commit
commit 74cd15cd02708c7188581f279f33a98b2ae8d322
Author: Zheng Liu <wenqing.lz@taobao.com>
Date: Mon Feb 18 00:32:55 2013 -0500
ext4: reclaim extents from extent status tree
Please note that my local rtorrent version was configured with
"--with-posix-fallocate". I'm not sure if distributions also enable this
flag, but it could explain why Ted and Dave weren't able to reproduce
the problem so far.
--
Markus
next prev parent reply other threads:[~2013-03-11 23:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 17:18 torrent hash failures since 3.9.0-rc1 Markus Trippelsdorf
2013-03-11 19:17 ` Markus Trippelsdorf
2013-03-11 19:41 ` Dave Jones
2013-03-11 20:13 ` Markus Trippelsdorf
2013-03-11 20:37 ` Theodore Ts'o
2013-03-11 20:46 ` Markus Trippelsdorf
2013-03-11 21:18 ` Theodore Ts'o
2013-03-11 21:38 ` Markus Trippelsdorf
2013-03-11 23:12 ` Markus Trippelsdorf [this message]
2013-03-11 23:26 ` Dave Jones
2013-03-12 3:00 ` Zheng Liu
2013-03-12 3:30 ` Theodore Ts'o
2013-03-12 3:44 ` Theodore Ts'o
2013-03-12 6:16 ` Markus Trippelsdorf
2013-03-12 6:44 ` Zheng Liu
2013-03-12 6:48 ` Markus Trippelsdorf
2013-03-12 7:16 ` Zheng Liu
2013-03-12 13:28 ` Theodore Ts'o
2013-03-13 10:15 ` Zheng Liu
2013-03-12 8:28 ` Sander
2013-03-12 22:04 ` Dave Chinner
2013-03-11 20:44 ` Dave Jones
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=20130311231227.GA319@x4 \
--to=markus@trippelsdorf.de \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@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).