Re: interesting problem

> What is DBPATH set to? After sweating this problem out today, we finally realized that all of the "good" directories have no parent directories in their heirarchy with more than 100 or so files. Any "bad" directory seems to a parent somewhere along the line with LOTS (100s) of directory entries. For example things will run while in "/u" but not in "/u/myhome". "/u" has 800+ entries, while it's parent "/" has only 30. Sounds like an AIX problem, someone knowledgeable suggested a corrupted file system. I do know that I've aged several years in the past few weeks. lol Thanks

I can't remember the command line option but if you use smit you can force a fsck on the /usr filesystem when the machine is rebooted, alternatively boot from the AIX media and run the fsck program. 'Cos the /usr is a journalled FS then it is not fsck on the way back, it relies on the logs to recover in the event of any error. What does errorpt say? If it is an 'inode' based problem then it should be reported. Smitty wrote: > > > What is DBPATH set to? > > After sweating this problem out today, we finally realized that all of > the "good" directories have no parent directories in their heirarchy > with more than 100 or so files. Any "bad" directory seems to a parent > somewhere along the line with LOTS (100s) of directory entries. For > example things will run while in "/u" but not in "/u/myhome". "/u" > has 800+ entries, while it's parent "/" has only 30. Sounds like an > AIX problem, someone knowledgeable suggested a corrupted file system. > I do know that I've aged several years in the past few weeks. lol > Thanks -- Paul Watson # Oninit Ltd # Growing old is mandatory Tel: +44 1436 672201 # Growing up is optional Fax: +44 1436 678693 # Mob: +44 7818 003457 # www.oninit.com #