Message-ID: <4223E9C8.5040604@utah-nac.org>
Date: Mon, 28 Feb 2005 21:04:24 -0700
From: jmerkey <jmerkey@utah-nac.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
MIME-Version: 1.0
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Parag Warudkar <kernel-stuff@comcast.net>,
       Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 bug
References: <1109487896.8360.16.camel@localhost> <200502271406.30690.kernel-stuff@comcast.net> <1109545130.7940.2.camel@localhost> <4223393D.3040908@utah-nac.org> <1109627454.7940.60.camel@localhost>
In-Reply-To: <1109627454.7940.60.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1060
Lines: 35

Jean-Marc Valin wrote:

>Le lundi 28 f?vrier 2005 ? 08:31 -0700, jmerkey a ?crit :
>  
>
>>I see this problem infrequently on systems that have low memory 
>>conditions and
>>with heavy swapping.    I have not seen it on 2.6.9 but I have seen it 
>>on 2.6.10. 
>>    
>>
>
>My machine has 1 GB RAM and I wasn't using much of it at that time (2GB
>free on the swap), so I doubt that's the problem in my case.
>
>	Jean-Marc
>
>  
>
Running the ext2 recover program seems to trigger some good bugs in 
2.6.10 with ext3 -- try it.  I was doing this
to test some disk tools and I managed to cause these errors with forcing 
ext2 recovery from an ext3 fs (which is
probably something to be expected.  The recover tools need to get 
syncrhonized -- have not tried with
mc yet.)    Doesn't happen every time though.

Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/