Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

W (1388) SPIFFS: Failed to update mtime (-10001) (IDFGH-13721) #14592

Open
3 tasks done
allacmc opened this issue Sep 17, 2024 · 1 comment
Open
3 tasks done

W (1388) SPIFFS: Failed to update mtime (-10001) (IDFGH-13721) #14592

allacmc opened this issue Sep 17, 2024 · 1 comment
Labels
Status: Opened Issue is new

Comments

@allacmc
Copy link

allacmc commented Sep 17, 2024

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Guys,

Why is this error occurring?

Would it be when the flash memory is full?

@espressif-bot espressif-bot added the Status: Opened Issue is new label Sep 17, 2024
@github-actions github-actions bot changed the title W (1388) SPIFFS: Failed to update mtime (-10001) W (1388) SPIFFS: Failed to update mtime (-10001) (IDFGH-13721) Sep 17, 2024
@pacucha42
Copy link
Collaborator

Hi @allacmc,
if I decode your report well, you are getting error -10001 on fopen/fstat call, and the file modification time is not updated in case of fopen. The error says your file system is full and SPIFFS cannot process any further operations (SPIFFS_ERR_FULL). You can enable SPIFFS debugging output using SPIFFS_DBG Kconfig option to see more details. I assume that cleaning your file-system or extending your SPIFFS partition size should be enough, but it's just a guess.

If this doesn't help, please provide more information about your application context (configuration, code excerpt with the failing sequence) and ideally also verbose logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

3 participants