Going through my Sage logs tracing down another problem I noticed the following has been occurring in the log for days.
Code:
Wed 7/28 0:48:46.343 [ProgressiveDeleter@17bc2e0] Starting progressive delete for:\\htpc\recordings2\TheOReillyFactor-6811281-1.ts
Wed 7/28 0:48:46.344 [ProgressiveDeleter@17bc2e0] Progressive deletion failed for:sage.u$a@a64162 reinserting it into the queue...
This is a file that was created last week when that channel was tuned briefly (file is only ~190MB) and it looks like Sage is having trouble deleting it. The file is indeed still there, named appropriately, not open in any other applications, and is not set to read only or have any weird permissions. Anyone have an insight into why Sage might be having trouble deleting the file?
Of course I can manually delete the file, but this is something Sage should be taking care of