/home directory full

Hi all,

I am working on a Sun OS v5.7. I have a home directory that is saying that it's full. The o/p is below.

....
/dev/dsk/c0t0d0s3 192833 108410 65140 63% /var
/dev/dsk/c0t0d0s7 4002513 161572 3800916 5% /free
/dev/dsk/c0t0d0s4 482824 434542 0 100% /home
/dev/dsk/c0t0d0s5 482824 268810 165732 62% /opt
.....

and actually the home has only some files in it. Could I have inadvertently done somethin ?

If this is not the problem, can you tell me how to increase the size of the home directory ? I still have space on my actual hard drive.

Thank you

Unless you are running some form of a jfs or DCE you are not going to be able to dynamically expqand the fileset. /home is what it is.
Now other users could have dumped too much in their home dirs; I would start there.

All the users will be /home/username, even if it's just a sym link.

Cheers.

Hi,

it seems the problem is of a greater nature.

the /home & the /tmp directory capacity seems to be varying dynamically.
Suddenly it shows like 1% full and if i run the 'ls -al' command again after a few minutes, it shows 100% or 60%, etc .

Could this be a virus ? Have any of you encountered anything like this before ?

Hi,

I tried to shutdown, powered off and restarted and had the same problem.

This is the o/p I got when it booted up and I ran fsck:

\usr
asked superblock wrong fix? Y - but it didn't because when I ran I ran fsck again I got same error

V

Oh my. You did remember to umount that filesystem before fsck'ing it right? Running fsck -- especially on SunOS -- with a mounted filesystem is "bad"(C)
Well the /tmp issue may just be a running process that uses /tmp as a sort of paging space -- to liken it to Winders. Perhaps log processing? I know that I wrote some large parsers which needed to open, write to, replace, etc. then copy back but I needed previous data to form a compare. After process was done, I deleted it, so I used /tmp space. I can't speak for the /home -- is that one alternatively full and empty as well? Running processes?

I have to mention of course, that I have seen hacked boxes which use various filesystems to store live traffic data prior to sending it out to an IRC channel. You may want to watch the connections with some permutation of netstat, or even install something like Snort to try and find a clue. Of course, crafting a tcpdump script should also suffice.

Good luck!

Oh, and if you fsck, remember to do it with the filesystem umounted.

Cheers.