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

LiitleFs made with Arduino-ESP-mklittlefs will not show any file #32

Open
gneiss15 opened this issue Aug 14, 2021 · 1 comment
Open

Comments

@gneiss15
Copy link

gneiss15 commented Aug 14, 2021

This Problem is (AFAIK) the same as described in Issue 28 & 31.
In my case, a FS made with mklittlefs from the Arduino-ESP8266 toolchain will show an empthy root-dir when mounted on the PC, but will work inside the esp.
If I made a fs as described in the readme, created files show up as expected.

Looking into both files (with a hex editor) it seams, that the first directory/file entry starts at a different position!

I will atach the file, that was created within the Arduino toolchain. It contains two files:

  • /html/index.html
  • /Config.json
    Both files can be accessed by the ESP.

(Just to clarify: Yes I do a "losetup /dev/loopX " and a "lfs /dev/loopX ")

One more remark:
The tool uses: pagesize=256 & blocksize=8192
Because I assumed that the problem lies in different asumptions about one of this parameters I try to use:
lfs -b 8192 /dev/loopX
This will issue:
No such file or directory
????

Feeder.ino.zip

@gneiss15
Copy link
Author

Arg, after looking into the source code I found the option must be given as:
-b=
So by doing a:
lfs -b=8192 /dev/loopX
everything works correct !!

So, that's a problem of the help displayed from "lfs -h", it doesn't show the necessary '=' (for all options with a value).
Because most (linux) programs expect such parameters without an equal sign, it is wise to show that the equal sign is needed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant