Ying-Hung Chen wrote:
We are seeing two (very similar?) kernel dumps (order:5, mode 0xd0 /
order:4 mode 0x50) on our systems,
the kernel didn't dump, this is just a backtrace. It is unable to allocate
enough contiguous memory to accommodate your extent list, so yes, it is
probably related to your fragmentation problem.
If you use the method I suggested previously for preallocating space, this
problem should go away.
I have search the mailing list and it seem to somehow related to the
fragmentation problem? (ours is at > 99%) though someone maintained this
is not Fatal, but our system usually becomes unresponsive when the dump
starts to appear (sometimes its ok after a while, but most of time it
just dumps forever and system becomes unusable and we have to reboot)
it's in a loop trying to allocate memory, and it can't.
are there fixes / workaround we can try?
Use preallocation, as I suggested.
Are these two message dump the same thing?