22 Nov
2004
22 Nov
'04
noon
Hi,
My hda1 partition is becoming %100 used and I don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use% Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21% /boot
MOUNT
/dev/hda2 on / type ext3 (rw)
FSTAB
LABEL=/ / ext3
defaults 1 1
LABEL=/boot /boot ext3
defaults 1 2
none /dev/pts devpts
gid=5,mode=620 0 0
none /proc proc
defaults 0 0
none /dev/shm tmpfs
defaults 0 0
/dev/hda3 swap swap
defaults 0 0
I looked for hints in /var/log/messages but didn't see
anything interesting. I didn't see any logs for
filesystems.
Could it be that ext3 is doing something to cause
this? Perhaps the filesystem needs to be checked.
At one point, I removed about two gigs of data and 'df
-H' reported available space at around 500MB. I'm not
sure what that might indicate.
I don't know anything about ext3 and how it works or
what it does but I guess that's where I'll start my
studies. Maybe it's a hardware problem with the HD. I
hope it isn't. If anyone has some clues about what I
should do or ideas for what might be happening, I
could really use the help.
ron
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
22 Nov
22 Nov
12:35 p.m.
On Mon, Nov 22, 2004 at 08:00:42AM -0800, R Parker wrote:
Hi,
My hda1 partition is becoming %100 used and I don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use% Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21% /boot
Maybe not related, but I suspect you have the default
"reserved blocks percentage" (5%). That would account
for the discrepancy between size / used / avail.
5% is 1.9 GB and that's a LOT of space to reserve for root.
You can set it with tune2fs, see the man page.
Could it be that ext3 is doing something to cause
this? Perhaps the filesystem needs to be checked.
couldn't hurt to fsck... well, it shouldn't ;-)
At one point, I removed about two gigs of data and
'df
-H' reported available space at around 500MB. I'm not
sure what that might indicate.
I've seen similar behavior with ext3 but I *think* in that
case I had a process that wouldnt' let go of the file.
THe space won't get actually freed while that's true.
Kill should fix that but IIRC it didn't. Reboot showed the
free space I expected.
--
Paul Winkler
http://www.slinkp.com
2:23 p.m.
--- Paul Winkler <pw_lists(a)slinkp.com> wrote:
I was hoping for something like that but booting
hasn't helped. I'll try again after the backups are
complete.
ron
On Mon, Nov 22, 2004 at 08:00:42AM -0800, R Parker
wrote:
I'm backing up now and expecting the worse case.
Hi,
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system
lockup
where I had to power cycle. I made about 9.7Gig
of
space available on the drive but after another
lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use%
Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21%
/boot
Maybe not related, but I suspect you have the
default
"reserved blocks percentage" (5%). That would
account
for the discrepancy between size / used / avail.
5% is 1.9 GB and that's a LOT of space to reserve
for root.
You can set it with tune2fs, see the man page.
Could it be that ext3 is doing something to
cause
this? Perhaps the filesystem needs to be checked.
couldn't hurt to fsck... well, it shouldn't ;-) At one point,
I removed about two gigs of data and
'df
-H' reported available space at around 500MB.
I'm
not
sure what that might indicate.
I've seen similar behavior with ext3 but I *think*
in that
case I had a process that wouldnt' let go of the
file.
THe space won't get actually freed while that's
true.
Kill should fix that but IIRC it didn't. Reboot
showed the
free space I expected. --
Paul Winkler
http://www.slinkp.com
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
12:45 p.m.
Hallo,
R Parker hat gesagt: // R Parker wrote:
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
Filling up can have many reasons. You should try to find out which are
the biggest files first:
$ du -sck * | sort -n
or similar can help you, if started from "/".
Maybe you want to do this from a boot disk like Knoppix.
Ciao
--
Frank Barknecht _ ______footils.org__
1:55 p.m.
Hi,
--- Frank Barknecht <fbar(a)footils.org> wrote:
Hallo,
R Parker hat gesagt: // R Parker wrote:
[root@stepdaddy /]# du -sckH * | sort -n
du: `proc/2392/fd/3': No such file or directory
1.4MB tmp
3.5GB usr
4.1kB initrd
4.1kB misc
4.9MB bin
13MB etc
13MB sbin
16MB boot
17kB
7kB lost+found
20GB home
33MB opt
36MB root
50kB tftpboot
112GB mnt
123MB lib
137GB total
435kB dev
727MB var
942MB proc
Nothing unexpected. The 112GB in mnt is on a seperate
disk array.
/dev/hda2 38GB 35GB 1.1GB 98% /
Home 20GB
usr/ 3.5GB
Let's say there's 25GB used, this leaves 13GB
unaccounted for.
I did find several hundred MB in core dumps but
nothing to account for 13GB is missing space.
ron
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system
lockup
where I had to power cycle. I made about 9.7Gig
of
space available on the drive but after another
lockup
and power cycle the drive is %100 used again.
Filling up can have many reasons. You should try to
find out which are
the biggest files first:
$ du -sck * | sort -n or similar can help you, if started from
"/".
Maybe you want to do this from a boot disk like
Knoppix.
Ciao
--
Frank Barknecht _
______footils.org__
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
6:46 p.m.
On Mon, Nov 22, 2004 at 09:55:18AM -0800, R Parker wrote:
[...]
I did find several hundred MB in core dumps but
nothing to account for 13GB is missing space.
i dont know if this is the same problem i have intermittently
with ext2. Sometimes du reports no free space, but i can still
write to it. Fsck doesnt fix it, but it goes away eventually
of its own accord.....?
cheers
--
Tim Orford
12:57 p.m.
On Mon, 22 Nov 2004 08:00:42 -0800 (PST), R Parker <rtp405(a)yahoo.com> wrote:
Hi,
My hda1 partition is becoming %100 used and I don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
You didn't mention whether or not you looked for actual files taking
up all the disk space. This might not be useful at all, but whenever
I'm trying to free up disk space, I use the following command to find
the directories that take up the most space:
du -m / | sort -n
This can take a long time before you see any output (because sort
needs du to finish).
Also, have you checked for any core files lying around? If you have a
process that's dumping core and being restarted, your disk can fill up
quickly. You can use find to remove any core files on disk:
find / -name "core.*" -exec rm {} \;
Be careful with that, especially if you run it as root.
Maybe you already did all this, but I always suspect the simple things
before something like an ext3 problem.
1:33 p.m.
Hallo,
Paul Coccoli hat gesagt: // Paul Coccoli wrote:
Also, have you checked for any core files lying
around? If you have a
process that's dumping core and being restarted, your disk can fill up
quickly. You can use find to remove any core files on disk:
find / -name "core.*" -exec rm {} \;
Oops, I'd say you should not run this at all: It will also find files
like "core.pd", "core.txt" or "core.c" which probably are
*not*
coredumps. Better use:
$ find / -name "core" -exec rm {} \;
Ciao
--
Frank Barknecht _ ______footils.org__
1:59 p.m.
--- Frank Barknecht <fbar(a)footils.org> wrote:
Hallo,
Paul Coccoli hat gesagt: // Paul Coccoli wrote:
I caught that one. :) I did 'find / -name "core"' and
manually removed the several dumps that were laying
around.
ron
Also, have you checked for any core files lying
around? If you have a
process that's dumping core and being
restarted,
your disk can fill up
quickly. You can use find to remove any core
files on disk:
find / -name "core.*" -exec rm {} \;
Oops, I'd say you should not run this at all: It
will also find files
like "core.pd", "core.txt" or "core.c" which
probably are *not*
coredumps. Better use: $ find / -name "core" -exec rm {} \;
Ciao
--
Frank Barknecht _
______footils.org__
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
1 p.m.
On Mon, Nov 22, 2004 at 08:00:42AM -0800, R Parker wrote:
Hi,
My hda1 partition is becoming %100 used and I don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
Look in /lost+found - the files you thought you'd deleted may be in there.
- Steve
1:18 p.m.
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
I once had a similar problem as I tried to scale a large image
in Gimp.
I killed Gimp after several minutes. After reboot, my machine
reported 0% disc space, because Gimp had placed a really huge
swapfile in my home directory.
Maybe you've got a similar problem? Try du to find out if
there are huge files on your drive.
Best regards
ce
11:53 p.m.
On Mon, Nov 22, 2004 at 08:00:42AM -0800, R Parker wrote:
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use% Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21% /boot
If you have a lot of small files on the disk somewhere, maybe you ran
out of inodes. Try "df -i" to see what percentage of inodes are still
available for use. If you've used them all up, I don't think you can
create more without recreating the filesystem with mke2fs, unfortunately.
Chuck
23 Nov
23 Nov
12:25 a.m.
If you only have just those two file systmes, / and /boot, then chances
are that the log files are big.
1) Check under /var/log
cd /var/log
ls -l
Check what big files you have there.
2) Check for unread email under /var/spool/mail or /var/mail
cd /var/spool/mail
ls -l
remove big email files.
3) Check what directories are using more space with:
cd /
du -sk * | more
It will show you how many KB each directory under / is using.
Then cd to each one and check again with du -sk * to see how much
space the subdirectories are using.
Then, you can isolate the file(s) that are using big space.
Next time, create a separate file system for /var.
GZS
Chuck Martin wrote:
On Mon, Nov 22, 2004 at 08:00:42AM -0800, R Parker
wrote:
My hda1 partition is becoming %100 used and I
don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use% Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21% /boot
If you have a lot of small files on the disk somewhere, maybe you ran
out of inodes. Try "df -i" to see what percentage of inodes are still
available for use. If you've used them all up, I don't think you can
create more without recreating the filesystem with mke2fs, unfortunately.
Chuck
12:56 a.m.
On Mon, Nov 22, 2004 at 11:23:36PM -0500, Gustavo J. Zamorano S. wrote:
If you only have just those two file systmes, / and
/boot, then chances
are that the log files are big.
The original poster's problem is that df -H shows lots of space
available, so the problem is not likely large files, but lots of
small files, which is why I suggested checking df -i, instead, to
see how many inodes are left.
Chuck
12:17 a.m.
Ron,
If this problem is real then there is a great little app called
'filelight' that gives you a physical representation of your hard
drive and will quickly tell you what directories hold all the files.
You can navigate your way down to the directory pretty easily and
quickly. Give it a try. I think it will help.
http://www.methylblue.com/filelight/filelight_0.6.3_2.png
http://www.methylblue.com/filelight/
I really like this little app. 1 picture - 1000 words - 1 Gazillion bytes.
Good luck,
Mark
On Mon, 22 Nov 2004 08:00:42 -0800 (PST), R Parker <rtp405(a)yahoo.com> wrote:
Hi,
My hda1 partition is becoming %100 used and I don't
know why. This began happening after a system lockup
where I had to power cycle. I made about 9.7Gig of
space available on the drive but after another lockup
and power cycle the drive is %100 used again.
[studio@stepdaddy studio]$ df -H
Filesystem Size Used Avail Use% Mounted
on
/dev/hda2 38GB 36GB 118MB 100% /
/dev/hda1 104MB 21MB 79MB 21% /boot
MOUNT
/dev/hda2 on / type ext3 (rw)
FSTAB
LABEL=/ / ext3
defaults 1 1
LABEL=/boot /boot ext3
defaults 1 2
none /dev/pts devpts
gid=5,mode=620 0 0
none /proc proc
defaults 0 0
none /dev/shm tmpfs
defaults 0 0
/dev/hda3 swap swap
defaults 0 0
I looked for hints in /var/log/messages but didn't see
anything interesting. I didn't see any logs for
filesystems.
Could it be that ext3 is doing something to cause
this? Perhaps the filesystem needs to be checked.
At one point, I removed about two gigs of data and 'df
-H' reported available space at around 500MB. I'm not
sure what that might indicate.
I don't know anything about ext3 and how it works or
what it does but I guess that's where I'll start my
studies. Maybe it's a hardware problem with the HD. I
hope it isn't. If anyone has some clues about what I
should do or ideas for what might be happening, I
could really use the help.
ron
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
7335
days inactive
7335
days old
linux-audio-user@lists.linuxaudio.org
14 comments
10 participants
participants (10)
-
Chuck Martin -
Frank Barknecht -
Gustavo J. Zamorano S. -
Mark Knecht -
mchristoph.eckert＠t-online.de -
Paul Coccoli -
Paul Winkler -
R Parker -
Steve Harris -
Tim Orford