[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <319012f0811051213g1f2ed31blf2b4bede3dd9535@mail.gmail.com>
Date: Wed, 5 Nov 2008 21:13:30 +0100
From: Cryptooctoploid <cryptooctoploid@...il.com>
To: "Theodore Tso" <tytso@....edu>
Cc: "Roc Valles" <vallesroc@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: data corruption with ext4 (from 2.6.27.4) exposed by rtorrent
On Wed, Nov 5, 2008 at 6:25 PM, Theodore Tso <tytso@....edu> wrote:
> 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.
Yes, -o nodelalloc resolves the issue here.
>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).
I have 2GB of memory and my machine is not under any kind of
memory pressure normally.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists