All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Cryptooctoploid <cryptooctoploid@gmail.com>
Cc: Roc Valles <vallesroc@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: data corruption with ext4 (from 2.6.27.4) exposed by rtorrent
Date: Wed, 5 Nov 2008 12:25:53 -0500	[thread overview]
Message-ID: <20081105172553.GA29880@mit.edu> (raw)
In-Reply-To: <319012f0811050534i27b7dce1t8120b3a343844adc@mail.gmail.com>

Cryptooctoploid,

Based on some reflection and further discussion on #ext4, I have a
theory which we need to try to prove/disprove that it may be related
to memory pressure combined with the delayed allocation code.

If you've already dismantled your ext4 setup, maybe you can't test
this, but it would be interesting to know mounting with the -o
nodelalloc makes the problem go away.  Also, how much memory do you
have in your system and is your system often under memory pressure?
(i.e., your system often uses swap, and where the amount of free
memory is often near the low water mark where it is trying to evict
memory either by dropping clean pages or writing dirty pages back to
the filesystem and/or swap).

						- Ted

  parent reply	other threads:[~2008-11-05 17:25 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
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 [this message]
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=20081105172553.GA29880@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.