/var/opt/OV/tmp/OpC

[Asad Malik]

When we try to change directory to /var/opt/OV/tmp/OpC it hangs forever. find command also hang when looking for a file in that directory. Can not kill those find command processes even with kill -9. Any suggestion why it has happenned.
Rest of the var filesystem is ok.
Thanks

[boley janowski]

wow your stats dont look too good, points to 37 out of 107 responses, whats up with that?

your issue, is the /var/opt/OV/tmp/OpC it own mount point?? usually the mount point is /var/opt/OV if this is the case what is happening at the mount point? do you have any filesystems full (bdf) is NNM and ITO up and running (ovstatus -c)?

provide some feed back and leave some points to poeple and you'll get much better responses from everyone.

[Asad Malik]

how can I see the points stat. is there a way to see all the ticket that I have opened so far and how many points have been assigned?

coming back to question
/var is the mount point. file system is not full (50%). NNM and ITO are up and running.

[boley janowski]

see where you name is under author, next to your question and each comment you make. click that and you will be able to see all the stats about your login.

to find your questions, you can select "search" under IT resource center. then type in your name on the search for line, and check the "forum" block. there maybe another way to do tis but im not aware of it.

question:
do you have any full file systems?
do you have anything eating up processor? run

top

this will give you a report of what processes are useing the most cpu resources as well as give you memory info and report the number of zombies you have out there.

are you having problems everywhere? just under var? or just under /var/opt/OV/tmp/OpC?

[Asad Malik]

no filesystem is full
no zombie processes
problem is only in /var/opt/OV/tmp/OpC directory in /var filesystem. All other directories in /var and /var/opt/OV/tmp are fine.

[boley janowski]

Sorry Asad,

It sounds like its a hardware issue if its not a file system full or overloaded processor, but that makes no sence if the rest of that file system is not having the same issue, the next possibility would be a bad sector on the disk, which happens to be where OpC is at, but if ITO is up and collecting data it writes to that dir. Im not sure if it will generate errors if it cant write to that file or if it just dumps the data, seems like you would get some more info. I dont have any more for you, Sorry!

[Asad Malik]

I have rebooted the box and all is ok. I can access that directory. Before reboot communication with ITO server was also down.

[boley janowski]

great,

i understood that ITO and NNM was up and running but you couldn't access that dir, didn't make any sence to me, but glad that all is well. Remeber to leave some sort of feed back on each entry, this will help your stats, and more will be willing to assist you if your stats are close response=feedback, you dont have to leave points for each answere if it doesn't relate, but leave the N/A for those so that you will still get credit for it in your stats.

[boley janowski]

http://us-support3.external.hp.com/estaff/bin/doc.pl/screen=estaffAssistance/sid=bd47626604077ea0a9/distrib_redir=2+989346865|*?Page=file0002#forstatus