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

Cannot retry fs mount command if first attempt failed #80024

Open
pahindman opened this issue Oct 17, 2024 · 2 comments · May be fixed by #80026
Open

Cannot retry fs mount command if first attempt failed #80024

pahindman opened this issue Oct 17, 2024 · 2 comments · May be fixed by #80026
Assignees
Labels
area: File System bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Milestone

Comments

@pahindman
Copy link

Describe the bug

When using the fs mount littlefs command, the command may fail, typically due to a typo in the mount point name. Unfortunately, once this happens it cannot be used again until resetting Zephyr.

To Reproduce

Steps to reproduce:

uart:~$ fs mount littlefs invalid_mount_point
Error mounting as littlefs: -22
uart:~$ fs ls
uart:~$ fs mount littlefs /mount_point
uart:~$ fs ls
uart:~$

Expected behavior

uart:~$ fs mount littlefs invalid_mount_point
Error mounting as littlefs: -22
uart:~$ fs ls
uart:~$ fs mount littlefs /mount_point
uart:~$ fs ls
mount_point/
uart:~$

Impact

It's a minor annoyance. I've fixed it locally, and plan on posting a PR shortly.

Logs and console output

Environment (please complete the following information):

  • OS: Ubuntu
  • Toolchain: Zephyr SDK
  • Commit SHA or Version used: 2bfc2a3

Additional context

@pahindman pahindman added the bug The issue is a bug, or the PR is fixing a bug label Oct 17, 2024
Copy link

Hi @pahindman! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

@de-nordic
Copy link
Collaborator

de-nordic commented Oct 18, 2024

Buge is present since release v2.0.0, severity set as low, even though this can lead to device lockup, it is in shell, and only triggered by user when memory gets low - so it is rather happening in developer env than on released devices.

@de-nordic de-nordic added this to the v4.0.0 milestone Oct 18, 2024
@de-nordic de-nordic added the priority: low Low impact/importance bug label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: File System bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants