root full

[Michael Thomas_1]

Any assistance on what to do when root partition is full and will not let telnet or web console access.????

[Christopher McCray_1 · Accepted solution]

Hello,

Are you also denied access from the normal console?? Have you tried booting into single-user mode or lvm maintenance mode?

Also, If you have an ignite tape that is firly recent, this will solve your problem by restoring to a previous state, but that may be a little drasticc.

Hope this helps

Chris

[K.Vijayaragavan.]

Hi,

get root previlege either by logging in on console (may be command line login option of cde)or booting in single user mode.
look for any "core" and "a.out" file just occupying more space in your root file system.by issuing,
"find / -name core -print"
"find / -name a.out -print"
remove those files.

purge rc.log and shutdown.log file if required.

-Vijay

[melvyn burnard]

If you can login to the system, start with the obvious, e.g. looking for normal files in /dev, etc.
Simple example:
cd /dev
du -s * |sort -n
look for large umbers, as a typical eeror is someone trying to do something to /dev/null and they get ot wrong (/dev/nul), or /dev/rmt/om instead of /dev/rmt/0m.

If you cannot login, I am afraid you will be forced to crash the system with an RS or a power off, then interrut th ereboot, bring it into single user mode, and start to investigate from there.

HTH

[Douglas Arneson]

Hi,

Assuming that you have console access look for files that could be canditates for removal with the command: find / -xdev -size +10000c -exec ll {} \; > /tmp/bigfiles

Page /tmp/bigfiles to find files to remove, typically log files. If +10000c returns too many files to review, increase the number to get a managable number of files.

Continue until you have removed enought files to gain access.

HTH,

Doug

[Shannon Petry]

Normally, root will still be allowed access. Normally, rlogin will be more effective than telnet (has to do with accounting and writing to ptmp, wtmp, etc...).

If you have a machine listed in /.rhosts, issue a rlogin as root from that machine.

Sometimes, this will hang for quite some time before letting you in. Depending on the boot time for the system, it is sometimes easier to hard power, and force single user mode from the IPL.

Then use the steps others gave to clear up the problem.


Regards,
Shannon

[Michael Thomas_1]

Thanks to all for the information. Initially we could not login from the web console or through a telnet session. What we ended up doing was going to the web console and putting in CTRL B. and going through the service processor to reset the system. After taking a look in / found that operator had tried to do a backup and the /dev/rmt/0m was not defined so it wrote the backup to /dev. Thanks again for the information...