Hi Everyone,

I have two partitions, / (root) and /home. When I try to put something
on / it says I'm out of space, which a df does show:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 2847752 2847752 0 100% /
/dev/hda2 3703644 260576 3251896 8% /home

But I can't find what's eating up everything... As soon as I move
something from / to /home and continue to check the free space, it gets
eaten up almost instantly, but I can't find what it is. When I do a
'du' on the / partition it shows I'm only eating up 1.7 Gigs, not the
2.7 Gigs I have total:

# du -h -x -s --exclude=home /
1.7G /

Any ideas? In my hunt for some large log file or something, I ran this
to find any files over 1 Meg in size, but nothing it spit out was a log
file nor anything out of the ordinary:
find -name '*' -size +1024k

So any ideas what this could be? This box is behind a firewall and
there's no way to get to it from the Internet, so I know it hasn't been
hacked. Also it's the only Linux box on our network, and with me being
the only person who uses Linux I know someone else hasn't screwed with
the box.

Thanks for any suggestions or ideas on what to check. It's running
Slackware 10.2.

Alex

"Alex" <samalex@gmail.com> wrote in message
news:1143145143.353953.247150@e56g2000cwe.googlegr oups.com

> But I can't find what's eating up everything... As soon as I move
> something from / to /home and continue to check the free space, it
> gets eaten up almost instantly, but I can't find what it is. When I
> do a 'du' on the / partition it shows I'm only eating up 1.7 Gigs,
> not the
> 2.7 Gigs I have total:
>
> # du -h -x -s --exclude=home /
> 1.7G /
>
> Any ideas?

"df -i" to see if there are any inodes left. Many small files can use up the
entire amount available.

On 23 Mar 2006 12:19:03 -0800, "Alex" <samalex@gmail.com> wrote:

>I have two partitions, / (root) and /home. When I try to put something
>on / it says I'm out of space, which a df does show:
>
>Filesystem 1K-blocks Used Available Use% Mounted on
>/dev/hda1 2847752 2847752 0 100% /
>/dev/hda2 3703644 260576 3251896 8% /home
>
>But I can't find what's eating up everything... As soon as I move

Take it down to single user, then run 'du -h --max-dep=1 /',
look for biggest directory, repeat moving into the biggest
directory until you see the culprit.

I'd expect runaway ... whatever I find Your / looks small for
a full 10.2 install?

Grant.
--
WinXP: Access Start->Turn Off Computer, then while holding Ctrl-Alt-Shift,
left click on Cancel. This terminates Windows Explorer...

ynotssor <ynotssor@example.net> did eloquently scribble:
> "df -i" to see if there are any inodes left. Many small files can use up the
> entire amount available.
>

Yes... but df without the -i would show free space even if there wasn't any
due to inodes.
--
-----------------------------------------------------------------------------
| spike1@freenet.co.uk | Windows95 (noun): 32 bit extensions and a |
| | graphical shell for a 16 bit patch to an 8 bit |
|Andrew Halliwell BSc(hons)| operating system originally coded for a 4 bit |
| in |microprocessor, written by a 2 bit company, that|
| Computer Science | can't stand 1 bit of competition. |
-----------------------------------------------------------------------------

Hi,

That might've been the case, but I rebooted and now I have that Gig of
HD space back

Thanks for the info though, if this happens again I'll definitely have
a starting point.

Sam

Alex wrote :

> Any ideas?

My guess is there's a process that has run amok and now is filling up
all space available in /tmp

Check if there's a lot of similar named files in /tmp and run 'strings
filename' on one of those to see if you can find which process created
the file and then stop this process.
--
Thomas O.

This area is designed to become quite warm during normal operation.

> So any ideas what this could be? This box is behind a firewall and
> there's no way to get to it from the Internet, so I know it hasn't been
> hacked. Also it's the only Linux box on our network, and with me being
> the only person who uses Linux I know someone else hasn't screwed with
> the box.

I've got a feeling it is not the case but check .xsession-errors, for root
in your case. That can grow without you noticing if you have a problem.

Pete


--
http://www.petezilla.co.uk

> Thanks for any suggestions or ideas on what to check. It's running
> Slackware 10.2.
>
> Alex

Maybe you could try one of the graphical disc usage tools, for instance
xdiskusage.

JB

Hi Everyone,

Thanks for all the great replies, and I'm making note of everything
incase this happens again.

I'm not sure exactly what ate-up that extra gig of HD space, but a
reboot fixed it. I'd rather have held off to find the cause, but I
needed the server working quickly.

Thanks again --

In alt.os.linux.slackware Alex <samalex@gmail.com> wrote:
: I'm not sure exactly what ate-up that extra gig of HD space, but a
: reboot fixed it. I'd rather have held off to find the cause, but I
: needed the server working quickly.

Since a reboot fixed it, this does point to something filling up /tmp,
which should be emptied on reboot. In the future, make sure to record
the output of ps and of top (top will spike a process up to the top of
the list if it's doing excessive I/O, ps might not show this). Also
look at the contents of /tmp as already posted. Another handy tool is
the fuser command. This will show you all processes accessing a given
partition at the moment.