Restart SQL. I've seen this a couple times at a client, never dug out the root cause (I suspect there's some non-SQL resource being held somewhere).
Irritating, I know.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability