From: Dave Jones <davej@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: 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 15:41:59 -0400 [thread overview]
Message-ID: <20130311194159.GB3579@redhat.com> (raw)
In-Reply-To: <20130311191753.GA439@x4>
On Mon, Mar 11, 2013 at 08:17:53PM +0100, Markus Trippelsdorf wrote:
> On 2013.03.11 at 18:18 +0100, Markus Trippelsdorf wrote:
> > I get hash failures on "completed" torrents since 3.9.0-rc1 (Linux 3.8
> > seems to be fine). What happens is that the torrents apparently complete
> > successfully. After reboot however the hash check fails and there are
> > missing (or corrupted) chunks. I've tested this with two different
> > clients (rtorrent and aria2c) and both are affected. So I think this
> > might be a filesystem issue.
> >
> > /dev/sda ext4 1.4T 666G 640G 51% /var
> > /dev/sda on /var type ext4 (rw,noatime,data=ordered)
> >
> > I use ECC memory (and there is nothing in the logs).
>
> To reproduce this issue just do the following:
>
> % wget http://torrents.linuxmint.com/torrents/linuxmint-12-gnome-cd-nocodecs-64bit.iso.torrent
> % rtorrent linuxmint-12-gnome-cd-nocodecs-64bit.iso.torrent
> (Wait until the torrent finishes)
> % sudo echo 3 > /proc/sys/vm/drop_caches
> (Rehash the torrent (Ctrl-R))
> The torrent doesn't rehash successfully and a few hunks are
> missing/corrupted and need to be downloaded again.
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 ?
Or maybe you could isolate it to a filesystem problem using something
like fsx ?
Dave
next prev parent reply other threads:[~2013-03-11 19:42 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 [this message]
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
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=20130311194159.GB3579@redhat.com \
--to=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).