Bugzilla – Bug 2513
Importing a file into a disk that is nearly full gives unhelpful error message
Last modified: 2020-09-05 05:49:52 UTC
Importing a file into a disk that is nearly full (a file to large for the remaining available space) gives unhelpful error message: >"Failed to add sample block" And the disk is left totally filled Setting this to P2 but it is marginal P1 This is a regression on 2.4.2 and earlier where we had a proper error trap abd this helpful error message: >Audacity failed to write to a file >Perhaps G: is not writable or the disk is full And in this case the space on disk is reclaimed with the project wound back to how it was before the aborted/failed import
This is also logged as as part of UP-25 https://wiki.audacityteam.org/wiki/Unitary_Project_-_issue_tracking#up25 I have assigned to Paul as he volunteered to fix the UP-25 issues
At https://github.com/audacity/audacity/commit/2389b191f637e60a0d025b46b9735dd7ee1ddc77 The error message is made more helpful, but that is not the entire complaint?
If part of the complaint is non-reclamation of disk space -- is the vacuuming on exit enough? Or maybe you find that vacuuming fails, because it requires sufficient space on the drive for a copy?
Testing on W10 with Audacity 3.0.0 70175ac - latest Master alpha This appears to be back to 2.4.2 behavior (not entirely perfect - but graceful, informative and can be dealt with) Following the Steps to reproduce At Step 2 I get the error message >Audacity failed to write to a file >Perhaps G: is not writable or the disk is full This is a much better error messaged and is I believe the same as we had in 2.4.2 So I am going to mark this as OK on Windows. Paul wrote: >The error message is made more helpful, but that is not the entire complaint? That was the "complaint" of this bug >If part of the complaint is non-reclamation of disk space -- >is the vacuuming on exit enough? > >Or maybe you find that vacuuming fails, because it requires sufficient >space on the drive for a copy? This would be a separate issue, as yet unlogged, and currently under discussion
Testing on macOS 10.15.6 Catalina with Audacity 3.0.0 70175ac latest Master alpha This appears to be back to 2.4.2 behavior Following the Steps to reproduce At Step 2 I now get the error message that we used to get in 2.4.2 (and some earlier) >Audacity failed to write to a file >Perhaps /Volumes/NO NAME/ is not writable or the >disk is full I shall mark this as OK on Mac
