All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Roc Valles <vallesroc@gmail.com>
Cc: Cryptooctoploid <cryptooctoploid@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: data corruption with ext4 (from 2.6.27.4) exposed by rtorrent
Date: Mon, 3 Nov 2008 08:40:08 -0500	[thread overview]
Message-ID: <20081103134008.GE29102@mit.edu> (raw)
In-Reply-To: <3d3ce57e0811030442o377cf2bet212eefba79d714bb@mail.gmail.com>

On Mon, Nov 03, 2008 at 12:42:11PM +0000, Roc Valles wrote:
> Some person already reported this. I'm having the same problem.
> http://marc.info/?l=linux-ext4&m=122557056518246&w=2
>
> rtorrent is a bittorrent client that makes heavy use of mmap instead
> of read/write to avoid needless duplication of data. It has exposed
> other bugs in the past (mmap bug in 2.6.19).
> http://libtorrent.rakshasa.no
> Downloading a big torrent (>2GB) with rtorrent triggers it more times
> than not. The bigger the torrent, the higher the likeliness of
> failure. When the torrent is finished, if a hash check is forced by
> pressing control-r on the torrent, some blocks will fail.

Can both of you send the output of "dumpe2fs -h /dev/<disk device>" of
the filesystem in question?  The thing which I'm most interested in is
whether the extents feature was enabled or not.  (i.e., was this a
freshly made ext4 filesystem, or a ext3 filesystem mounted under ext4,
and with which features eanbled?)

Thanks,

						- Ted

  reply	other threads:[~2008-11-03 13:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 12:42 data corruption with ext4 (from 2.6.27.4) exposed by rtorrent Roc Valles
2008-11-03 13:40 ` Theodore Tso [this message]
2008-11-03 13:47   ` Cryptooctoploid
2008-11-03 14:09   ` Roc Valles
2008-11-03 15:34   ` Cryptooctoploid
2008-11-03 15:51     ` Jindrich Makovicka
2008-11-05 19:44       ` Solofo.Ramangalahy
2008-11-05 19:57         ` Theodore Tso
2008-11-05 20:09           ` Solofo.Ramangalahy
2008-11-05 20:21             ` Solofo.Ramangalahy
2008-11-05 20:42               ` Theodore Tso
2008-11-05 20:52                 ` Solofo.Ramangalahy
2008-11-06 10:15                 ` Aneesh Kumar K.V
2008-11-06 10:36                   ` Solofo.Ramangalahy
2008-11-06 13:47                     ` Solofo.Ramangalahy
2008-11-06 13:59         ` Aneesh Kumar K.V
2008-11-05 13:34   ` Cryptooctoploid
2008-11-05 16:16     ` Eric Sandeen
2008-11-05 17:25     ` Theodore Tso
2008-11-05 20:13       ` Cryptooctoploid
2008-11-06  9:00       ` Roc Valles
2008-11-06  9:31       ` Cryptooctoploid

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=20081103134008.GE29102@mit.edu \
    --to=tytso@mit.edu \
    --cc=cryptooctoploid@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=vallesroc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.