https://bugzilla.novell.com/show_bug.cgi?id=231220 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|seife@novell.com | ------- Comment #10 from seife@novell.com 2007-01-14 05:19 MST ------- I have rebuilt my filesystems, they were all with 1k blocksize due to the yast2 bug until close-to-goldmaster-10.2. I can no longer get the machine to hang now (but it was not too clearly reproducible before...). My _uneducated_ guess what happened is: - write performance was abysmal due to ext3 with 1k blocksize - nfs reads with 10mb/second into (highmem?) fs cache - ext3 tries to write out, performance is bad - something in ext3 needs lowmem (inode cache maybe? something that needs much more space due to the 1k blocksize?) - now somewhere in a driver (with interrupts turned off, because it does not even react to sysrq) memory needs to be allocated, but it does not succeed. Maybe the lowmem accounting is wrong somewhere, so that there _should_ be memory free to use, but isn't? - With the 4k blocksize it does not happen, because the disk simply is much faster writing out than the network is filling the buffers? With the 1k blocksize, the machine was also very "jumpy" before locking up, means that i had latencies of 10's of seconds in the console when doing anything (ls for example), which would IMO support the "memory pressure" theory. This could of course be totally off topic :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.