From: Dave Chinner <david@fromorbit.com>
To: Sander <sander@humilis.net>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
"Theodore Ts'o" <tytso@mit.edu>, Dave Jones <davej@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: torrent hash failures since 3.9.0-rc1
Date: Wed, 13 Mar 2013 09:04:52 +1100 [thread overview]
Message-ID: <20130312220452.GR21651@dastard> (raw)
In-Reply-To: <20130312082854.GA1515@panda>
On Tue, Mar 12, 2013 at 09:28:54AM +0100, Sander wrote:
> Markus Trippelsdorf wrote (ao):
> > On 2013.03.11 at 16:37 -0400, Theodore Ts'o wrote:
> > > We actually run fsx in a number of different configruations as part of
> > > our regression testing before we send Linus a pull request, and
> > > haven't found any issues. So unless it's a hardware problem, it seems
> > > unlikely to me that your running fsx would turn up anything.
> >
> > Yes, I let it run for a while anyway and it didn't report any failure.
>
> > Please note that my local rtorrent version was configured with
> > "--with-posix-fallocate".
>
> Would it be possible to enhance fsx to detect such an issue?
fsx in xfstests already uses fallocate() for preallocation and hole
punching, so such problems related to these operations can be found
using fsx. The issue here, however, involves memory reclaim
interactions and so is not something fsx can reproduce in isolation. :/
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-03-12 22:04 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
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 [this message]
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=20130312220452.GR21651@dastard \
--to=david@fromorbit.com \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=sander@humilis.net \
--cc=tytso@mit.edu \
/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