My problem is a hanging (non responsive) system when a core file is about
to be created on a ramdisk booted X86 SLES SP1 platform.
The ramdisk is small (ramdisk_size=70000) and the size of the core
file is a lot bigger than that. It does not matter if the application
produces the core due to e.g. a SIGSEGV or if it is forced by e.g.
assert() or abort() calls. On top of this there is a /export tmpfs filesystem
which is the "working" directory of the application and the directory
where the core file is actually placed. Everything works fine if
"ulimit -c" is set to 0 or less size than the ramdisk. What is interesting is
that creating a file in /export using dd or similar that is equal the
real size of the core seems to work without problem. So, then why
does the system hang when creating the core file?
Is the core file temporarily created on / or any other place that is
affected by the ramdisk size before moved to target folder?
It at least seems to me that the ramdisk size is the limiting factor
for the kernel core dump file creation routine!?
A similiar (read not identical kernel modules) system booted from HDD works fine I might add
Is there some way of overcoming this issue ( the ramdisk can _not_
be increased in size
) or is this a bug that have no current known
workarounds. Is this in fact a bug or is there a vital kernel module
missing? Any hints or ideas what might be wrong?