Ticket #4 (closed defect: wontfix)

Opened 4 years ago

Last modified 2 years ago

Failed: There is not enough space on the disk

Reported by: jw113 Owned by: Garrett
Priority: major Milestone: Eraser 5.8.9
Component: Core Version: 5.8.6a
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

I've been using Eraser since at least 5.80, and never had a problem -- until now. I'm using 5.86a under Vista SP1 RC1, and I'm trying to erase a nearly 4gb file (4,294,966,784 bytes) from an external 40gb USB HD formatted as FAT32. When Eraser gets to the 99% point it stops and reports

Information:
  Statistics:
    Erased area         =  4092 MB
    Cluster tips         =  0 bytes

    Data written         =  4092 MB
    Write time         =  207.09 s
    Write speed         =  20232 kB/s

Failures:
  Failed: I:\MJ\TI1.tib (There is not enough space on the disk.)

In fact the disk has 24gb free, and chkdsk shows no problems with it. I'm wondering if Eraser is getting confused with a file that is so close to the 4gb FAT32 limit? Or???

Thanks.

Blocking

IdSummaryMilestone
#4Failed: There is not enough space on the diskEraser 5.8.9

Blocked by

IdSummaryMilestone
#4Failed: There is not enough space on the diskEraser 5.8.9

Change History

comment:1 Changed 4 years ago by Joel

Looking through other issues pointed me to the fix: Disable erasing of "Cluster tip area". Then the erase succeeds.

But why does leaving this option enabled cause a "disk full" error?

comment:2 Changed 4 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel

FAT32 chokes on files larger than 4GB. When you do a cluster tip erase you may exceed the 4G mark if the file already is 4GB long.

Ahwell, one of those quirks.

Joel

comment:3 Changed 4 years ago by Joel

  • Status changed from accepted to assigned
  • Milestone set to Eraser 5.87

comment:4 Changed 4 years ago by Joel

  • Owner changed from Joel to Garrett

OK I can't really fix it. This is where definitions kinda fail and Garrett I'll need your intervention. To erase the cluster tip the file size is rounded up to the next cluster. Now what happens when adding this last cluster will cause the file to reach the file size limit of FAT32?

Joel

comment:5 Changed 2 years ago by Joel

  • Component set to Core
  • Milestone changed from Eraser 5.8.8 to Eraser 5.8.9

comment:6 Changed 2 years ago by eraser_user

same problem in version 6.0.6.1376

comment:7 Changed 2 years ago by Joel

  • Status changed from assigned to closed
  • Resolution set to wontfix
Note: See TracTickets for help on using tickets.