Unless you are normally running CHECKDB (a recommended practice to catch these problems early on and reduce downtime/risk of data loss) and can look at the historical runs for how long it takes to run, there isn't a whole lot that you can do except wait it out. If you stop it, you won't get the information that you need to help resolve the problems.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]