Ticket #281 (closed defect: fixed)

Opened 8 months ago

Last modified 5 months ago

File is currently in use and cannot be removed

Reported by: trejkaz Owned by: Joel
Priority: major Milestone: Eraser 6.0.7
Component: Core Version: 6.0.6.1376
Keywords: Cc:
Blocked By: Blocking:
Operating System: Windows 7 Processor Architecture:

Description

Today I tried to erase free space on C:, and got the following error in the logs overnight. In the morning, C: had less than 1MB disk space free and a huge number of large files under this directory which it failed to delete.

After this error occurred I manually had Eraser shred the directory and it appears to be proceeding normally.

Thursday, 17 December 2009 11:48:49 AM	Error	The file C:\=Ja[Ns{h3V0XLQVtJ!jA6-{QbT7BrWq(\ 2MYGhOijfP+}k1]_'_g8vl7X9weG![sUI+ 7eFHkklnP7p=`mY(9F}SPOjaCF(AhXtOBq_-mjhhdShyZ!FrG'W[wPo7ko1th`3BiXUc]-_GEkdc+sl}h9xTajxCo6G!y~cjYZ2RiR-_j3UadfBH[UD[-74,H4}coD}6[8Qv`2E()0etI`Tj4YAG4InYq5=S0zzo7Qy0bEV[]`)gcx2{b W,!+{) is currently in use and cannot be removed.

I'm fairly sure this will be something like Windows trying to index the file after it was created, or something equally daft. I see this sort of error in the app I develop for work, and the standard workaround is to wait some period of time and try again. In the case of Eraser it seems like it could continue to try and delete other files and move the failed ones to the end of the queue to retry later.

Blocking

IdSummaryMilestone
#281File is currently in use and cannot be removedEraser 6.0.7

Blocked by

IdSummaryMilestone
#281File is currently in use and cannot be removedEraser 6.0.7

Change History

Changed 7 months ago by Joel

  • milestone set to Eraser 6.0.7

Changed 7 months ago by Joel

  • owner set to Joel
  • status changed from new to accepted

Currently we already try 50 tries, at 100ms intervals. What else do you suggest we do?

Changed 7 months ago by Joel

  • status changed from accepted to pending

Changed 6 months ago by trac-robot

  • status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Changed 5 months ago by Joel

  • status changed from closed to reopened

Changed 5 months ago by Joel

  • status changed from reopened to accepted

Changed 5 months ago by Joel

  • status changed from accepted to closed
  • resolution set to fixed

Potential fix in r1871

Note: See TracTickets for help on using tickets.