As specified in the FatFs documentation, FatFs f_lseek() has a different policy for reporting the file size when moving to an offset above SEEK_END. POSIX reports the actual file size of the write, whereas FatFs reports the size at the seeked position.
As a specific impact, when SQLite is used with FatFs, it reports error code 26SQLITE_NOTADB when the database is opened.
As specified in the FatFs documentation, FatFs
f_lseek()
has a different policy for reporting the file size when moving to an offset aboveSEEK_END
. POSIX reports the actual file size of the write, whereas FatFs reports the size at the seeked position.As a specific impact, when SQLite is used with FatFs, it reports error code
26
SQLITE_NOTADB
when the database is opened.Reference URL