Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
no space on disk
- Thread starter inq1
- Start date
fredericofonseca
IS-IT--Management
boot in single user
man find
There will be some examples there
Regards
Frederico Fonseca
SysSoft Integrated Ltd
man find
There will be some examples there
Regards
Frederico Fonseca
SysSoft Integrated Ltd
- Thread starter
- #3
How do you know the problem is in /dev ?
For me, if you're on OSR 5.0.X, the root filesystem is full.
If a root account is already logged, then try:
rm /tmp/* /usr/tmp/*
As you are done, you may execute this:
killall -t 10 15
killall
As you suspect /dev (backup on mistyped device name ?), you may try this:
find /dev -type f ! -name .marrylock -exec ls -l {} \;
Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
For me, if you're on OSR 5.0.X, the root filesystem is full.
If a root account is already logged, then try:
rm /tmp/* /usr/tmp/*
As you are done, you may execute this:
killall -t 10 15
killall
As you suspect /dev (backup on mistyped device name ?), you may try this:
find /dev -type f ! -name .marrylock -exec ls -l {} \;
Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
- Thread starter
- #5
The reason I figured it was on /dev is because of the message above. Could this be a large file resulting from a print job? The printers stopped working first.
I cannot get the find command to work that you gave me.
Any more ideas, and I sure appreciate your help.
I cannot get the find command to work that you gave me.
Any more ideas, and I sure appreciate your help.
- Thread starter
- #6
- Status