Re: kcore eating my disk space
Hi, David Gardiner wrote: > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > [EMAIL PROTECTED]:/# du -hs * Try "du -x / | sort -g | less". bye, Roman
Re: kcore eating my disk space
Hi, David Gardiner wrote: > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > root@munchkin:/# du -hs * Try "du -x / | sort -g | less". bye, Roman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
On Wed, 2002-10-16 at 14:24, David Gardiner wrote: > Thanks Andrew, Olaf and Scott for your quick replys, > > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > [EMAIL PROTECTED]:/# du -hs * > 2.6Mbin > 2.9Mboot > 4.0kcdrom > 68k dev > 9.4Metc > 4.0kfloppy > 7.7Ghome > 4.0kinitrd > 18M lib > 16k lost+found > 4.0kmnt > du: `proc/580/fd/3': No such file or directory > 257Mproc Of course all these files tend to cluster together - for maximum effect I would be looking to reduce that 7.7G. Since you posted to debian-laptop, I guess you're using one. I'd imagine it is pretty normal on most laptops that /home would end up with all the crap too :-) Here's mine, for example: kant:/# du -hs * 2.5Mbin 11M boot 4.0Kcdrom 124Kdev 22M etc 4.0Kfloppy 29G home 4.0Kinitrd 20K lan 23M lib 16K lost+found 4.0Kmnt 4.0Kmusic 14M opt 4.0Kphotos 20K plato 3.1Gpostgres du: `proc/15126/fd/3': No such file or directory 516Mproc 43M root 6.6Msbin 3.0Mtmp 32K user 3.5Gusr 2.9Gvar I've decided it's cheaper to spend money on a bigger HD than to spend time on removing cruft though. Now when I go looking for cruft I can look for really big cruft, making it correspondingly easier to find. Cheers, Andrew. -- - Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)916-7201 MOB: +64(21)635-694OFFICE: +64(4)499-2267 Survey for free with http://survey.net.nz/ -
Re: kcore eating my disk space
On Wed, 2002-10-16 at 14:24, David Gardiner wrote: > Thanks Andrew, Olaf and Scott for your quick replys, > > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > root@munchkin:/# du -hs * > 2.6Mbin > 2.9Mboot > 4.0kcdrom > 68k dev > 9.4Metc > 4.0kfloppy > 7.7Ghome > 4.0kinitrd > 18M lib > 16k lost+found > 4.0kmnt > du: `proc/580/fd/3': No such file or directory > 257Mproc Of course all these files tend to cluster together - for maximum effect I would be looking to reduce that 7.7G. Since you posted to debian-laptop, I guess you're using one. I'd imagine it is pretty normal on most laptops that /home would end up with all the crap too :-) Here's mine, for example: kant:/# du -hs * 2.5Mbin 11M boot 4.0Kcdrom 124Kdev 22M etc 4.0Kfloppy 29G home 4.0Kinitrd 20K lan 23M lib 16K lost+found 4.0Kmnt 4.0Kmusic 14M opt 4.0Kphotos 20K plato 3.1Gpostgres du: `proc/15126/fd/3': No such file or directory 516Mproc 43M root 6.6Msbin 3.0Mtmp 32K user 3.5Gusr 2.9Gvar I've decided it's cheaper to spend money on a bigger HD than to spend time on removing cruft though. Now when I go looking for cruft I can look for really big cruft, making it correspondingly easier to find. Cheers, Andrew. -- - Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)916-7201 MOB: +64(21)635-694OFFICE: +64(4)499-2267 Survey for free with http://survey.net.nz/ - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
In linux.debian.laptop, you wrote: > ps: I have 256 M of ram and 320M is around the sum of my ram and the > swap space thats being used so I assume it's the combined total of > memory that the kernel is using. So I probably don't want to get rid of > it do I :) just of my root partition if it was still there or appears in > the future when we have our next blue moon. kcore should never increase in size. It is the size of physical RAM, and does not include swap (incidentally, if you want to search for text in memory for debugging purposes, then you have to grep both /proc/kcore and the swap device, /dev/hdAB) 2 possiblities I can think of: 1) Some weird bug in the kernel? 2) You just backup/restored from from tape, /proc is not mounted for some bizaare reason, and you are trying to write a real file to the /proc directory which is not a proc file system yet. How many partitions do you have? What is your df -k output? Bizaare. -- TimC -- http://astronomy.swin.edu.au/staff/tconnors/ Entropy isn't what it used to be.
Re: kcore eating my disk space
In linux.debian.laptop, you wrote: > ps: I have 256 M of ram and 320M is around the sum of my ram and the > swap space thats being used so I assume it's the combined total of > memory that the kernel is using. So I probably don't want to get rid of > it do I :) just of my root partition if it was still there or appears in > the future when we have our next blue moon. kcore should never increase in size. It is the size of physical RAM, and does not include swap (incidentally, if you want to search for text in memory for debugging purposes, then you have to grep both /proc/kcore and the swap device, /dev/hdAB) 2 possiblities I can think of: 1) Some weird bug in the kernel? 2) You just backup/restored from from tape, /proc is not mounted for some bizaare reason, and you are trying to write a real file to the /proc directory which is not a proc file system yet. How many partitions do you have? What is your df -k output? Bizaare. -- TimC -- http://astronomy.swin.edu.au/staff/tconnors/ Entropy isn't what it used to be. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
David Gardiner <[EMAIL PROTECTED]> writes: > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > [snip command output] > > So if I trust du, df and ls in the /proc (which i probably shouldn't) > directory why did it start using the disk? > or show up as using disk space? I'd use `df` to get a handle on what partition is filling up and then `du -s` on that partition to figure out what is hogging it. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 LPIC-2 -- I hack, therefore I am -- BOFH
Re: kcore eating my disk space
Thanks Andrew, Olaf and Scott for your quick replys, The reason I noticed it was because my used disk space jump up to 100% and I started looking for what using it. du in the root directory gave [EMAIL PROTECTED]:/# du -hs * 2.6Mbin 2.9Mboot 4.0kcdrom 68k dev 9.4Metc 4.0kfloppy 7.7Ghome 4.0kinitrd 18M lib 16k lost+found 4.0kmnt du: `proc/580/fd/3': No such file or directory 257Mproc and ls -las gave me, 262573 -r 1 root root 268349440 Oct 16 08:59 kcore and *now* [EMAIL PROTECTED]:/# du -hs /proc/ du: `/proc/865/fd/4': No such file or directory 1.0k/proc and [EMAIL PROTECTED]:/proc# ls -als kcore 0 -r1 root root 320598016 Oct 16 10:51 kcore and my disk space has dropped to it's previous level So if I trust du, df and ls in the /proc (which i probably shouldn't) directory why did it start using the disk? or show up as using disk space? ps: I have 256 M of ram and 320M is around the sum of my ram and the swap space thats being used so I assume it's the combined total of memory that the kernel is using. So I probably don't want to get rid of it do I :) just of my root partition if it was still there or appears in the future when we have our next blue moon. Dave Scott Barnes wrote: On Wed, 16 Oct 2002 09:20:40 +1000 David Gardiner <[EMAIL PROTECTED]> wrote: what is /proc/kcore and why is it eating up my disk space? It's not, it's a virtual file, it's actually the running kernel. i.e. 262573 -r1 root root 268349440 Oct 16 08:59 kcore and a couple of minutes later 0 -r1 root root 320598016 Oct 16 09:03 kcore ^ ^ || and why is it's size 0 blks and also have a size of 320598016 bytes i'm running with kernel 2.4.17 It's 0 blocks because it isn't actually on the disk, it's in memory. Yeah the obvious answer from it's name is it's a kernel core dump, but It's not a core *dump*, it's the actual core :) thats just a guess! a real explanation would be good and how do I get rid of it would be better. Thanks, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
David Gardiner <[EMAIL PROTECTED]> writes: > what is /proc/kcore and why is it eating up my disk space? > i.e. > 262573 -r1 root root 268349440 Oct 16 08:59 kcore > and a couple of minutes later > 0 -r1 root root 320598016 Oct 16 09:03 kcore > ^ ^ > || > and why is it's size 0 blks and also have a size of 320598016 bytes > i'm running with kernel 2.4.17 > > Yeah the obvious answer from it's name is it's a kernel core dump, but > thats just a guess! a real explanation would be good and how do I get > rid of it would be better. The `files' below /proc are not real files. They are a file oriented interface to information that lives in your running kernel. I would think kcore gives (read-only) access to the memory currently used. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 LPIC-2 -- I hack, therefore I am -- BOFH
Re: kcore eating my disk space
On Wed, 16 Oct 2002 09:20:40 +1000 David Gardiner <[EMAIL PROTECTED]> wrote: > what is /proc/kcore and why is it eating up my disk space? It's not, it's a virtual file, it's actually the running kernel. > i.e. > 262573 -r1 root root 268349440 Oct 16 08:59 kcore > and a couple of minutes later > 0 -r1 root root 320598016 Oct 16 09:03 kcore > ^ ^ > || > and why is it's size 0 blks and also have a size of 320598016 bytes > i'm running with kernel 2.4.17 It's 0 blocks because it isn't actually on the disk, it's in memory. > > Yeah the obvious answer from it's name is it's a kernel core dump, but It's not a core *dump*, it's the actual core :) > thats just a guess! a real explanation would be good and how do I get > rid of it would be better. > Thanks, > Dave > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Reeve the cat - -BEGIN FORTUNE- You have no real enemies. --END FORTUNE-- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d? s: a? C UL P+ L E- W++ N o K- w--- O M-- V-- PS+++ PE Y PGP t+++ 5 X+ R+++ tv+ b+++ DI++ D+ G e* h-- r+++ y** --END GEEK CODE BLOCK-- pgpQkEqeRh1gR.pgp Description: PGP signature
Re: kcore eating my disk space
David Gardiner <[EMAIL PROTECTED]> writes: > The reason I noticed it was because my used disk space jump up to 100% > and I started looking for what using it. du in the root directory gave > > [snip command output] > > So if I trust du, df and ls in the /proc (which i probably shouldn't) > directory why did it start using the disk? > or show up as using disk space? I'd use `df` to get a handle on what partition is filling up and then `du -s` on that partition to figure out what is hogging it. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 LPIC-2 -- I hack, therefore I am -- BOFH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
Thanks Andrew, Olaf and Scott for your quick replys, The reason I noticed it was because my used disk space jump up to 100% and I started looking for what using it. du in the root directory gave root@munchkin:/# du -hs * 2.6Mbin 2.9Mboot 4.0kcdrom 68k dev 9.4Metc 4.0kfloppy 7.7Ghome 4.0kinitrd 18M lib 16k lost+found 4.0kmnt du: `proc/580/fd/3': No such file or directory 257Mproc and ls -las gave me, 262573 -r 1 root root 268349440 Oct 16 08:59 kcore and *now* root@munchkin:/# du -hs /proc/ du: `/proc/865/fd/4': No such file or directory 1.0k/proc and root@munchkin:/proc# ls -als kcore 0 -r1 root root 320598016 Oct 16 10:51 kcore and my disk space has dropped to it's previous level So if I trust du, df and ls in the /proc (which i probably shouldn't) directory why did it start using the disk? or show up as using disk space? ps: I have 256 M of ram and 320M is around the sum of my ram and the swap space thats being used so I assume it's the combined total of memory that the kernel is using. So I probably don't want to get rid of it do I :) just of my root partition if it was still there or appears in the future when we have our next blue moon. Dave Scott Barnes wrote: >On Wed, 16 Oct 2002 09:20:40 +1000 >David Gardiner <[EMAIL PROTECTED]> wrote: > > > >>what is /proc/kcore and why is it eating up my disk space? >> >> > >It's not, it's a virtual file, it's actually the running kernel. > > > >>i.e. >>262573 -r1 root root 268349440 Oct 16 08:59 kcore >>and a couple of minutes later >> 0 -r1 root root 320598016 Oct 16 09:03 kcore >> ^ ^ >> || >>and why is it's size 0 blks and also have a size of 320598016 bytes >>i'm running with kernel 2.4.17 >> >> > >It's 0 blocks because it isn't actually on the disk, it's in memory. > > > >>Yeah the obvious answer from it's name is it's a kernel core dump, but >> >> >It's not a core *dump*, it's the actual core :) > > > >>thats just a guess! a real explanation would be good and how do I get >>rid of it would be better. >>Thanks, >>Dave >> >> >> >>-- >>To UNSUBSCRIBE, email to [EMAIL PROTECTED] >>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >> >> >> > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
David Gardiner <[EMAIL PROTECTED]> writes: > what is /proc/kcore and why is it eating up my disk space? > i.e. > 262573 -r1 root root 268349440 Oct 16 08:59 kcore > and a couple of minutes later > 0 -r1 root root 320598016 Oct 16 09:03 kcore > ^ ^ > || > and why is it's size 0 blks and also have a size of 320598016 bytes > i'm running with kernel 2.4.17 > > Yeah the obvious answer from it's name is it's a kernel core dump, but > thats just a guess! a real explanation would be good and how do I get > rid of it would be better. The `files' below /proc are not real files. They are a file oriented interface to information that lives in your running kernel. I would think kcore gives (read-only) access to the memory currently used. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 LPIC-2 -- I hack, therefore I am -- BOFH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kcore eating my disk space
On Wed, 16 Oct 2002 09:20:40 +1000 David Gardiner <[EMAIL PROTECTED]> wrote: > what is /proc/kcore and why is it eating up my disk space? It's not, it's a virtual file, it's actually the running kernel. > i.e. > 262573 -r1 root root 268349440 Oct 16 08:59 kcore > and a couple of minutes later > 0 -r1 root root 320598016 Oct 16 09:03 kcore > ^ ^ > || > and why is it's size 0 blks and also have a size of 320598016 bytes > i'm running with kernel 2.4.17 It's 0 blocks because it isn't actually on the disk, it's in memory. > > Yeah the obvious answer from it's name is it's a kernel core dump, but It's not a core *dump*, it's the actual core :) > thats just a guess! a real explanation would be good and how do I get > rid of it would be better. > Thanks, > Dave > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Reeve the cat - -BEGIN FORTUNE- You have no real enemies. --END FORTUNE-- -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d? s: a? C UL P+ L E- W++ N o K- w--- O M-- V-- PS+++ PE Y PGP t+++ 5 X+ R+++ tv+ b+++ DI++ D+ G e* h-- r+++ y** --END GEEK CODE BLOCK-- msg09038/pgp0.pgp Description: PGP signature
