On Sat, 2002-09-07 at 22:14, Tzafrir Cohen wrote: > > TThe system probably had enough swap available, and there were no > OOM-killer messages in the log. Syslog seemed to work and the xinetd > master process managed to do something. So I tend to rule out any > out-of-memory situation. Seems like some kernel bug. > It does seem like some kind of severe kernel memory leak (ouch!) but I dio not think ext3 actually has anything to do with it - it's a symptom not the cause. The messages you see simpyl state that the ext3 code could not allocate memory. This does not mean that it is it to blame for not freeing it.
Can you try to give the output of vmstat on the machine during normal operation and when it reaches this state? Gilad. > > I originally converted the system from ext2 to ext3 after someone pressed > the reset button, at a very inconvinient time, and reducing the downtime > in such cases seemed useful. > > My question is: is the version of ext3 in 2.4.18 (or that specific > mandrake kernel) considered stable? If so: any ideas how to debug this? > (although I'll probably just go back to ext2). > > If not: could someone recommend a stable version? (or ext2?) > > Thanks > > -- > Tzafrir Cohen > mailto:[EMAIL PROTECTED] > http://www.technion.ac.il/~tzafrir > > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > -- Gilad Ben-Yossef <[EMAIL PROTECTED]> http://benyossef.com "Your /linuxrc sucks worse than MSExchange - that's the only way you could run out of anon devices at that point." -- linux/fs/super.c ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
