Ah, that is good sleuthing.
"At the moment I'm tempted to just change the unix timestamp and give myself some time to work out if I can delete safely." Hah - I thought of the same thing. If this were one of my servers, that is what I would do to buy time and get those from repeatedly filling up space.
Another way might be just to edit deletion in progress flag, presumably 1 means in progress and so what would 0 do? I'm not sure actually. You could check in the code for that to see what those values mean and would likely do.
The tracker talks about how the deletion of specific modules works in the recycle bin as opposed to the deletion of the whole course. So clearly then, that is your situation here since the courses still exist. Something is holding up the module deletion. The good news then is that it is not deadlock issue in the recycle bin between module and its course (which is not uncommon in the case of deleting categories and courses.)
"At the moment I'm tempted to just change the unix timestamp and give myself some time to work out if I can delete safely." Hah - I thought of the same thing. If this were one of my servers, that is what I would do to buy time and get those from repeatedly filling up space.
Another way might be just to edit deletion in progress flag, presumably 1 means in progress and so what would 0 do? I'm not sure actually. You could check in the code for that to see what those values mean and would likely do.
The tracker talks about how the deletion of specific modules works in the recycle bin as opposed to the deletion of the whole course. So clearly then, that is your situation here since the courses still exist. Something is holding up the module deletion. The good news then is that it is not deadlock issue in the recycle bin between module and its course (which is not uncommon in the case of deleting categories and courses.)