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

fs_mount for FAT FS does not distingush between no file system and other errors #33142

Closed
de-nordic opened this issue Mar 8, 2021 · 1 comment
Assignees
Labels
area: File System bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@de-nordic
Copy link
Collaborator

Describe the bug
The fs_mount is supposed, when option enabled, to create new file system on a device if mount fails due to non-existing file system.

To Reproduce
Steps to reproduce the behavior:

  1. modify test/subsys/fs/fat_fs_api/prj_native_posix.conf by replacing
    CONFIG_DISK_FLASH_DEV_NAME="flash_ctrl"
    with
    CONFIG_DISK_FLASH_DEV_NAME="flash_ctrl_bla"
  2. west build -b native_posix --build-dir mkfs_err zephyr/tests/subsys/fs/fat_fs_api/ -- -DCONF_FILE=prj_native_posix.conf
  3. mkfs_err/zephyr/zephyr.elf
  4. Observe multiple
    E: fs mount error (-5)
    as the fs_mount tries to mount the file system and then create file system on non-existent device.

Expected behavior
Distinguish when there is device error and when there is no-file system error; exist when there is device error and attempt to mkfs when there is no file system.

Environment (please complete the following information):

  • OS: Linux
  • Toolchain Zephyr sdk 0.12
  • Commit SHA Zephyr: 554101e
@de-nordic de-nordic added bug The issue is a bug, or the PR is fixing a bug area: File System labels Mar 8, 2021
@de-nordic de-nordic self-assigned this Mar 8, 2021
@nashif nashif added the priority: low Low impact/importance bug label Mar 8, 2021
@de-nordic
Copy link
Collaborator Author

Configuration problem. Not an issue.

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

No branches or pull requests

2 participants