I had to simply power the box off and on. The test team had been using the system on Friday with no issues, but they tried to sign on today with reported telnet errors, no response to ping and the console was non-active.
Powering off/on a UNIX system is a killer, it is not a PC with MS...
You have no other choice but to go single user /maintenance level and use fsck on all the file systems before you can mount them...
(Hope you will not need your backups...)
Never have used that filesystem but the others that I have used have always cleared themselves on reboot if the machine was set up correctly.
Single user, as VBE suggests, is the first step but since the filesystems didn't auto clean you may have deeper problems. Do you have emergency boot capabilities that would allow cleaning of all filesystems.