• Q: Linux tells me there is not enough memory left on /ffx or /ffxusr respectively although there should be free memory left.
  • A: In the special case of interacting with the internal flash-devices (see root file system it might happen that not all memory will be freed immediately after erasing some date-files. The reason is the process pdflush running on the system. This special daemon-process is responsible for handling the memory-writebacks and flash-handling. Thus when erasing large files it is presumable that it needs a couple of time until pdflush has finished its work and you can use the whole flash-memory.

  • Q: The directory /ffx has only 16MByte diskspace but I created a file with a total size larger then 16MByte. How is this possible.
  • A: The filesystem /ffx is using is the so called JFFS2 which is capable of compressing data.

  • Q: What does the jffs2_scan_eraseblock message mean?
    $ dmesg
    ... 
    jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0e8: 0xfd23 instead
    jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0ec: 0xdf7f instead
    jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0f0: 0xd9ca instead
    ...
    $
    
  • A: This errormessage does not affect the camera's functionality.
    It means that there are some bitpattern not matching the expected free block pattern.
    One reason could be an old bootloader in combination with a new firmware (→ Linux: Tarball update).