You should check with df if your filesystems are full, /var or maybe /tmp. And maybe increase them or clean up by moving, deleting or compressing, whatever suits your needs.
I have checked that too by df -h and the space consumed is very less on both /tmp and /var and also on other mount points as well.... is there any size limitation set for cron file such that it cant have more than xxxKB?????
Wherever that cronjob is putting the files, that directory is full. As Zaxxon says, either clean out old files or increase the size of the directory. I would recommend doing both.
Not sure what your cronjob is doing but if you want to edit and you have sudo rights you can run sudo crontab -e and that will allow you to edit your cronjobs. Be very careful in there, if you're not familiar with how to edit it you can mess things up.
*EDIT* Just noticed your reply to Zaxxon. How many cronjobs do you have running?
Please post the exact version of Linux/Unix concerned.
Please check inode consumption. You may have too many files.
df -i
If you have sar, please check basic kernel limits.
sar -v
2 : Kernel version
4 : The major revision of the kernel
21 : The minor revision of the kernel
57 : Immediate fixing / bug fixing for critical error
ELsmp....
Sorry guys as i was looking at some other box.... i got the reason as /var has 100%... Thanks nixnoob for posting the link of Danesh project... it was really useful and now i have fixed the problem... Thanks everyone for sorting this issue..