Weblog entry #5 for sneex

kcore is 256T! (or Debian AMD64 forty days later)
Posted by sneex on Mon 27 Aug 2007 at 23:27
Tags: none.
[Debian 4 on AMD64 64-Bits]

For the longest time everything under AMD64 appears quiet; until today I noticed a 256T (tera bytes!) /proc/kcore file on one of my servers ... 256T?

I realize that /proc/kcore doesn't truly take any real disk space on the server but I always thought that kcore 'size' was supposed to match 'real memory' size (which should be 8GB on the server in question -- not 256T!)

Thoughts? Comments? Opinions?

 

Comments on this Entry

Posted by sneex (63.139.xx.xx) on Fri 19 Oct 2007 at 00:24
[ Send Message | View sneex's Scratchpad | View Weblogs ]
Hmmm, another some odd 40 days and the /proc/kcore file is again at 256T ... very weird. While I have not yet identified the issue I am thinking there is a pattern ...

The other two systems have not -yet- exhibited this behavior...

very strange ... -Sx-
http://youve-reached-the.endoftheinternet.org/

[ Parent | Reply to this comment ]

Posted by Anonymous (194.105.xx.xx) on Mon 22 Oct 2007 at 10:02
I have the same problem. Did you manage to find what went wrong?
Thank you.

[ Parent | Reply to this comment ]

Posted by Anonymous (194.105.xx.xx) on Mon 22 Oct 2007 at 10:39
Well i found out what went wrong in my case. I had mounted a partition over an older folder. Then i started downloading something into that folder. It worked ok until i got a disk full error. I checked with df but the new partition was reported empty. But the root partition was reported as full. I checked with du -sh all the folders in / but if I summed up all except /proc I couldn't make up the space on the root partition. Anyhow, after a reboot (without mounting the additional partition) the df reported the space correctly and I have seen that /var had the rest of the space. The mount point was /var/srv/Indexes and somehow the data got downloaded onto the root partition instead of the new partition mounted there. In fact after i got the disk full error that folder was behaving strange. If i issued a ls i got the right listing. but if i tried to do a cd in one of the new downloaded folders i would get not found error (even if ls reprted them there...). I suppose it had something to do with rights over the mount point or something. Regarding the /proc/kcore it was the only thing i could find to blame at that point. Now i know that doesn't use any space on the disk.

[ Parent | Reply to this comment ]