Blender 3.6 'Insufficient disk space' reported incorrectly #111537
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#111537
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: Radeon (TM) Pro WX 5100 Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context FireGL 21.30.18 30.0.13018.2
Blender Version
Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash:
e53e55951e7aWorked: (newest version of Blender that worked as expected)
Short description of error
Blender 3.6 seems to work well however if your free space in the blender folder is insufficient to save to new model file, Blender reports an ‘error: no such path or directory’ rather than an ‘Insufficient Space’; subsequently it will not save the file and any auto-saves can result in corrupted file space.
Exact steps for others to reproduce the error
This is not a render output problem but an error which occurs when you have insufficient disk space on which to save the file.
System = Win 11, latest build on a Dell 5820 with 80gb DRAM. Previously was using 3.4 version after trying and removing 3.5., 3.6.2 works well.
To produce the error I was saving a 3.6 version .BLEND file to a new name. File was 1.7gb with, I discovered, only 1.4 tb of free space on the disk.
This is not an operational bug but rather an error reporting/logging bug since the error reports a ‘not found save-file path’ rather than an ‘insufficient space’ error.
After removing old .blend2 and .blend3 versions of previous models, I freed up 98gb of file space on the drive. The save or ‘save as’ procedure now works just fine.
During the error investigation I found that the autosaves (I have it set for 30 minute intervals where models and ‘saves’ are being sent to the d: drive) were also being corrupted and, if I applied them, they then corrupted my updated model.
It also corrupted segments of my c/:drive where the ‘blender foundation’ files are held. I was able to track this down by using an ‘scf /scannow’ command drive
Hi @Terrence-4 , are you saying that insufficient space on disk will lead to corrupted autosave files? This probably needs fixing as it fails silently in your case.
Also " File was 1.7gb with, I discovered, only 1.4 tb", I guess both are 'GB' right? 😅
Blender doesn't differentiate these situations from what I can recall, it will just report the generic "I'm not able to write to this path" message.
Hi @YimingWu,
Thank you for helping.
Yes, typo not terabytes but gigabytes.
Yes, the new file I was trying to save to was 1.7gb but the disk available space (discovered later) was only 1.4 gb.
two problems while trying to save a file but there is not enough space on the disk:
Re: error message, I think this can be improved
Re: file corruption, it is not clear if the drive or software is culprit here for auto-save file corruption.
In any case, I'll forward this report devs
Thank you Pratik,
I cannot say for sure Blender corrupted the drive.
I can say that this Dell 5820 is used a good 10 hr/day plus weekends for hard computes including Blender. The 'C' volume, i.e. the corrupted volume, is used only for system programs. Data/image storage, temp files, data etc are all on other images. I have 64GB of DDR4 RAM & the C volume image is on a 256GB Class 40 SSD.
The system has been in continual use since 12/2020 and I have never had corrupted segments on it until this instance was found & corrected by an SCF command call.
Dang, but Windows 11 and SSD's are very stable.