[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 13/09/10 16:16, Keith Abraham wrote:
On 13/09/10 15:19, Simon Waters wrote:This is universally the size of memory, being as it is a mapping of memory except..... 64bit AMD machines (virtual) have 128TB for /proc/kcore This seems wrong, and the nice folk in the LKML were discussing a similar issue in June 2009. Anyone know if this is simply a kernel bug or did someone deliberately decide to make it a stupid size? Anyone have a 64bit system, especially AMD, where the size of /proc/kcore is the size of RAM, and if so which kernel are you running please? All the reports seem to be AMD64 circa 2.6.32I'm using kernel 2.6.35-4 and my /proc/kcore is 128.0 TiB also. AFAIK this is the file that gets dumped by the kernel when there is a crash. Like all /proc file it isn't a real file but i suppose it has to be represented as very large just in case the memory dump is huge.
Max size of memory dump = total RAM + total swap, no? Considering the maximum amount of DISK space people have at the moment is < 4TB, this seems just a little mad to me. Unfortunately I'm still waiting for my AMD64 board to come back from repair so I can't test atm.
And I'd hate to see what happens if it tries to dump all 128TB of that. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq