Messages in this thread | | | Date | Sun, 27 Mar 2005 12:17:06 -0800 | From | Badari Pulavarty <> | Subject | Re: [Ext2-devel] Re: OOM problems on 2.6.12-rc1 with many fsx tests |
| |
Badari Pulavarty wrote:
> Mingming Cao wrote: > >> On Sat, 2005-03-26 at 16:23 -0800, Mingming Cao wrote: >> >>> On Fri, 2005-03-25 at 14:11 -0800, Badari Pulavarty wrote: >>> >>>> On Fri, 2005-03-25 at 13:56, Andrew Morton wrote: >>>> >>>>> Mingming Cao <cmm@us.ibm.com> wrote: >>>>> >>>>>> I run into OOM problem again on 2.6.12-rc1. I run some(20) fsx >>>>>> tests on >>>>>> 2.6.12-rc1 kernel(and 2.6.11-mm4) on ext3 filesystem, after about 10 >>>>>> hours the system hit OOM, and OOM keep killing processes one by >>>>>> one. I >>>>>> could reproduce this problem very constantly on a 2 way PIII >>>>>> 700MHZ with >>>>>> 512MB RAM. Also the problem could be reproduced on running the >>>>>> same test >>>>>> on reiser fs. >>>>>> >>>>>> The fsx command is: >>>>>> >>>>>> ./fsx -c 10 -n -r 4096 -w 4096 /mnt/test/foo1 & >>>>> >>>>> >>>>> I was able to reproduce this on ext3. Seven instances of the above >>>>> leaked >>>>> 10-15MB over 10 hours. All of it permanently stuck on the LRU. >>>>> >>>>> I'll continue to poke at it - see what kernel it started with, which >>>>> filesystems it affects, whether it happens on UP&&!PREEMPT, etc. >>>>> Not a >>>>> quick process. >>>> >>>> >>>> I reproduced *similar* issue with 2.6.11. The reason I say similar, is >>>> there is no OOM kill, but very low free memory and machine doesn't >>>> respond at all. (I booted my machine with 256M memory and ran 20 copies >>>> of fsx on ext3). >>>> >>>> >>> >>> Yes, I re-run the same test on 2.6.11 for 24 hours, like Badari see on >>> his machine, my machine did not go to OOM on 2.6.11,still alive, but >>> memory is very low(only 5M free). Killed all fsx and umount the ext3 >>> filesystem did not bring back much memory. I will going to rerun the >>> tests without the mapped read/write to see what happen. >>> >>> >> >> >> Run fsx tests without mapped IO on 2.6.11 seems fine. Here is >> the /proc/meminfo after 18 hours run: > > > Mingming, Reproduce it on 2.6.11 with mapped IO tests. That will tell > us when the regression started.
Sorry - Ignore my request, Mingming already did this work and posted the result.
Thanks, Badari
- 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/
| |