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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

root-directory full?

Status
Not open for further replies.

woche

Programmer
Jan 16, 2002
25
CH
hi
1.: When I submit an "ls -al" command on the root-directory the system just spins, gives me no listing or error-message. Strangely, "ls" works. The "ls -al" command works on all the other directories. Is it possible, that there's no more room in my root-directory?

2.: My /var directory keeps filling up. I added additional space to the filesystem several times now, but since I'm doing a lot of REXX-tracing it seems to be filling up all the time. The problem here, I don't really know which directories use that much space in order do clean them.

thx
woche
 
woche,

Well what does df -k / report in terms of space used?

In /var a file to keep an eye on is wtmp, this logs all logins to the system and if you do not have any housekeeping routines can grow to a large size.

If you wish to view it :

cd /var/adm

who wtmp

to clear it down

> wtmp

Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
 
thanks - the /var problem is solved, %Used has dropped down to 68%.

for the root-problem:
df -k / returns:
Filesystem 1024-blocks Free %Used Iused %Iused
/dev/hd4 16384 5180 69% 1460 18%
Mounted on
/
this looks like there's still some space left.
 
woche,

Do other ls flags works i.e.

ls -ltr

Cheers

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
 
some do:
ls -a : works
ls -l : doesn't
ls -t : doesn't
ls -r : works
ls -e : doesn't
ls -f : works

thx
woche


 
Woche,

Can you post up a simple ls?

It sounds vert strange, no logical reason for some flags not to work....

Try this:

cd /

ls -ld .

Cheers

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
 
the 'ls -ld .' brings the following:
drwxrwxr-x 23 bin bin 1024 Nov 28 11:46 .
the 'ls' this:
/ : ls
.sh_history def
17cc0ba0f57d25a3909eb5e274c.jpg dev
DIR env_e
TT_DB etc
audit home
backup image.data
bin inst.log
bosinst.data lib
cd lost+found
cdrom lpp
data mnt
/ : ls
.sh_history
17cc0ba0f57d25a3909eb5e274c.jpg
DIR
TT_DB
audit
backup
bin
bosinst.data
cd
cdrom
data
def
dev
env_e
etc
home
image.data
inst.log
lib
lost+found
lpp
mnt
opt
pcmsdim
sbin
tftpboot
tmp
u
unix
usr
var

well, maybe I have to live with it;-)
thx




 
Is this a large file:

17cc0ba0f57d25a3909eb5e274c.jpg

I would zap it, everything seems o.k. from your ls -ld.

Cheers PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
 
thanks a lot for your help. although it didn't quite solve all my problems i still learned a lot.
thx
woche
 
woche,

No problem - I would state the an fsck of the root filesystem in maintenance mode may help there could be some
sort of inode problem. Does the ls -l ever return do one and
leave it running, see what happens.

Also what version of bos.rte.commands are you using? post up

lslpp -l |grep bos.rte.commands

Cheers

PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
 
okay, eventually I did a reboot of my UNIX -> it works again - why ever that might be!
by the way: the ls -l never returned, i let it run for quite some time.
thx for all the help
woche
 
woche,

one thing to look into on your /var filesystem is in the 'preserve' sub directory (/var/preserve)

This is where 'failed' or 'crashed' vi seesion are stored.
These files normally start with a capital 'E', and are usually quite large.

I normally just remove any of these after a day or two.
 
yes, you're right. there are indeed quite a few very large files! I'll get rid of those to...thanks!
woche
 
Hi,

1.Sometimes /var/ gets filled by a system "vmcore.X" files,that are created after the system crash.Those are HUGE !!!!

2.The "ls -la /" problem looks to me like a "/" filesystem corruption,which was fixed by a fsck that runs automatically on boot.
 
To list large files in /var (or any where..) type:

ls -al |sort -n +4

This will list the files in order of size (the file at the bottom being the biggest)

 
Try a "du" in /var, that will list all the files and sizes thereof in the /var and subdirectories for you. A bit tedious to browse through, but it does the job. IBM Certified Specialist - MQSeries
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top