size of /proc/kcore grows?
From: Christian (evil_at_g-house.de)
Date: 03/04/05
- Previous message: Andrew Morton: "Re: Linux 2.6.11.1"
- Next in thread: Christian Kujau: "Re: size of /proc/kcore grows?"
- Maybe reply: Christian Kujau: "Re: size of /proc/kcore grows?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 04 Mar 2005 23:37:49 +0100 To: linux-kernel@vger.kernel.org
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Andrew Morton: "Re: Linux 2.6.11.1"
- Next in thread: Christian Kujau: "Re: size of /proc/kcore grows?"
- Maybe reply: Christian Kujau: "Re: size of /proc/kcore grows?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
