From: Theodore Ts'o <tytso@mit.edu>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: 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: Mon, 11 Mar 2013 16:37:38 -0400 [thread overview]
Message-ID: <20130311203738.GB15478@thunk.org> (raw)
In-Reply-To: <20130311201334.GA444@x4>
On Mon, Mar 11, 2013 at 09:13:34PM +0100, Markus Trippelsdorf wrote:
> On 2013.03.11 at 15:41 -0400, Dave Jones wrote:
> > Worked fine for me on two separate machines. Could it be a network problem
> > perhaps ? If something is mangling the packet before it hits the disk,
> > that would explain it. What NIC do you use ?
I'm not a torrent expert, but I thought it did enough checksumming
such that if the packet got mangled, it would get noticd by the
torrent client before it writes the chunks to disk?
> > Or maybe you could isolate it to a filesystem problem using something
> > like fsx ?
>
> I've found fsx on your homepage, but I've no idea on how to use this
> tool. Any pointers?
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.
Can you send a dumpefs -h of the file system in question, and what
mount options (if any) you are using? Thanks!!
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?
- Ted
next prev parent reply other threads:[~2013-03-11 20:37 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 [this message]
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
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=20130311203738.GB15478@thunk.org \
--to=tytso@mit.edu \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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).