At 07:41 PM 4/27/2003 +0200, Mike Galbraith wrote:
>At 10:29 AM 4/27/2003 -0700, Martin J. Bligh wrote:
>> >> > To reproduce this 100% of the time, simply compile virgin 2.5.68
>> >> > up/preempt, reduce your ram to 128mb, and using gcc-2.95.3 as to not
>> >> > overload the vm, run a make -j30 bzImage in an ext3 partition on a
>> >> > P3/500 single ide disk box. No, you don't really need to meet all of
>> >> > those restrictions... you'll see the problem on a big hairy chested
>> >> > box as well, just not as bad as I see it on my little box. The first
>> >> > symptom of the problem you will notice is a complete lack of swap
>> >> > activity along with highly improbable quantities of unused ram were
>> >> > all those hungry cc1's getting regular CPU feedings.
>> >>
>> >> Yes, that's why I don't use ext3 ;-) It's known broken, akpm is fixing
>> >> it.
>> >
>> > I'm not at all convinced (must say I wouldn't mind at _all_ being
>> > convinced) that it's ext3... that just _seems_ to be worst easily
>> > reproducible case for some un-(expletive deleted)-known reason.
>>
>>Well, that's easy to test. Mount the fs as ext2, and see if it goes away.
>
>
>Sure, btdt very first thing, and that's why I'm not convinced that ext3 is
>the core problem. I see "it" in ext2 as well, just less so.
P.S. I'm fishing for hints. I'm (severely) hooked by the problem.
-
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/
This archive was generated by hypermail 2b29 : Wed Apr 30 2003 - 22:00:26 EST