-
Notifications
You must be signed in to change notification settings - Fork 3k
remove non empty directory returns inconsistent error codes between LittleFS & FatFS #5653
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
Labels
Comments
Thanks for reporting this issue. According to Open Group, this should actually be ENOTEMPTY. |
This was referenced Feb 16, 2018
ARM Internal Ref: MBOTRIAGE-794 |
Thanks @geky. This should be resolved in 5.9. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempting to remove/delete a non-empty directory from the FS returns different error codes when using FatFS vs LittleFS
Bug
Target
K64F
Toolchain:
GCC_ARM
Expected behavior
The same error code will be returned for both file systems
Actual behavior
When trying to remove a non-empty directory using FatFS: error code = EACCES
When trying to remove a non-empty directory using LittleFS: error code = EINVAL
Steps to reproduce
remove a non empty directory using FatFS and then using LittleFS
@geky
The text was updated successfully, but these errors were encountered: