Currently /co cancel only works on rollbacks which haven't started. It would be very useful for servers with large databases to cancel an ongoing rollback/lookup.

Fr wth, 10 minute lookup taking eons

Lookups and rollbacks should typically only take a couple seconds. If lookups/rollbacks/restores are taking a significant amount of time, or your database is repeatedly stating it's busy, you make have some other issue going on, such as extremely slow IO speeds.

If a command is repeatedly providing slow lookup times for you, please provide the exact command, so I can investigate further.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.