Very Computer

Can anyone help me to resolved the root (/) and /proc partition being full?
I notice the / is 101% and /proc 100% full.   How can I reduce the
size of these mentioned when I don't know which files/folders I should
delete?  Before noticing these size, it was at 92% on / and 100% /proc.  I
tried to backup the / partition using this command
.  pax w f /dev/rmt0 ..  Instead of doing backup, I saw the message
/ write failed, system full.  Can anyone help me, please?
I thank you in advanced.

Quote:> Can anyone help me to resolved the root (/) and /proc partition being
full?
> I notice the / is 101% and /proc 100% full.

Ignore /proc.  It's special.  Read the proc(4) man page for more.

Quote:>   How can I reduce the
> size of these mentioned when I don't know which files/folders I should
> delete?

Try maybe du(1)?  If /var is not on its own partition, you probably
have a lot of stuff under /var that's swamping the root (/) partition.
You'll need to find out what's taking up the space before you can do
anything about it.

I suggest "df -k /" to find out the number of kbytes being used in
the root partition.  Then "du -ks /var" to find the number of kbytes
being used under /var (assuming that /var is on the root partition).
If most of the space being taken up is there, then you know more about
where to look.

Quote:>  Before noticing these size, it was at 92% on / and 100% /proc.  I
> tried to backup the / partition using this command
> .  ?pax -w -f /dev/rmt0 .?.  Instead of doing backup, I saw the
message
> / write failed, system full.  Can anyone help me, please?

Backups don't delete what they're storing, so even if pax worked, it
would not have reduced the disk usage.  You need to find out what's
taking up the space before blindly trying to archive it.  For all you
know right now, it could be a whole bunch of temporary files somewhere
under /var that don't need to be backed up...

--

Targeting & Attack Radar                                  The Air Force
Air Force Research Labs                                   doesn't exist.
Senior Systems Administrator

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Well, the first most critical thing to do is free up some space on root.
Bring the system up in single-user mode.  Is /var on its own disk partition?
System log files are written into /var and if it's on root (not a good idea
for this exact reason), then that would explain how it got filled up.
You'll need to run "du -k /" to get an idea of what's being used where.

Regards,

Pete Howell

I would add only one more thing (see below please)

Quote:> ...
> delete?  Before noticing these size, it was at 92% on / and
100% /proc.  I
> tried to backup the / partition using this command
> .  pax w f /dev/rmt0 ..  Instead of doing backup, I saw the
message
> / write failed, system full.  Can anyone help me, please?

If you didn't have a type-o here and REALLY did try to write
to /dev/rmt0, there should be a big file called rmt0 under /dev.  In
Solaris, the usual (but by no means required) tape device files
are /dev/rmt/# where # is something like 0, 0l, 0mn, etc...
The /dev/rmt# format is the default for AIX so if you are more used to
AIX, than this could explain what is happening in /.

Good Luck!
                           -dt

--
WARNING!  All usenet posts from me are my opinion and no one else's
(necessarily).

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.