All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: size of /proc/kcore grows?
Date: Fri, 04 Mar 2005 23:37:49 +0100	[thread overview]
Message-ID: <4228E33D.5010505@g-house.de> (raw)

hi,

i've just tried to "search for something in the RAM", so i thougt 
/proc/kcore would be a good address to start. i really only wanted to 
grep for raw data throught it, i did not need any specific meta-data.

ok, i checked:

$ ls -lah /proc/kcore
-r--------  1 root root 256M Mar  4 23:25 /proc/kcore

which makes sense, since i have 256MB RAM.

$ su -
Password:
root$ cp /proc/kcore /data/Incoming/
`/proc/kcore' -> `/data/Incoming/kcore'
root$ ls -la /proc/kcore /data/Incoming/kcore
-r--------  1 root root 1.0G Mar  4 23:26 /data/Incoming/kcore
-r--------  1 root root 1.0G Mar  4 23:27 /proc/kcore

whooha! /proc/kcore and its new on-disk copy are now both 1GB in size.
how comes? i could imagine, that when "cp" tried to copy /proc/kcore the 
RAM gets filled with /proc/kcore again, thus doubling it...somehow...but 
cp continued with no errors, why should it double /proc/kcore 
(256MB->512MB) and then again (512MB->1024MB), but stop after this? i 
would've expected cp to never stop copying...

i don't get it,
Christian.




             reply	other threads:[~2005-03-04 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 22:37 Christian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:21 size of /proc/kcore grows? Christian Kujau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4228E33D.5010505@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.