Every time you do a sysdba or sysoper operation there is an operating system audit file generated. This includes sys as sysdba and rman backups. Check syslog.conf for where they are going and show parameter audit_trail. These can really add up after a period of time.

sorry guys , i don't know what i do this file system is increased
and i just remove the old logs i can't find any thing if the issue is with DISKGROUP why there is no issue
in node 2 ??? how i kill any process from writing in /home ????

There is likely more than one thing wrong. Did you check the note that Osama posted? That fits the error you see in the alert log. Do you have lsof on your system? sb's idea of seeing what is open and killing that off is a good one, although if some runaway forms (or something) process is rapidly opening and closing new files that could be confusing.

Some background processes open and close the same trace files, making them huge, since the filename is based partly on the process id. I sometimes do simple-minded searches like ls -Rl|sort -nrk5 (on my system, that recursively searches directories and sorts files by size, your system may have different commands to do the same thing), sometimes it makes it obvious what is going wrong (like having giant shared server process trace files on a little XE system). There may also be some adrci and xml things to clean up, I don't know much about that. Sometimes merely taking a long time to cd to a trace directory could be a clue there are thousands of unnecessary files there. Sometimes simply creating a file that is a long listing of all the files on the device and looking at it can identify the problem.

okay guys , i will send an email to my manager first to tell him we have bug in our system and we need to apply patch
but for a temporary sol can i delete the alert log files and then oracle can generated