fatfs v0.12b September 04, 2016:

- Improved f_rename() to be able to rename objects with the same name but case.
- Fixed an error in the case conversion teble of code page 866. (ff.c)
- Fixed writing data is truncated at the file offset 4GiB on the exFAT volume. (appeared at R0.12)
- Fixed creating a file in the root directory of exFAT volume can fail. (appeared at R0.12)
- Fixed f_mkfs() creating exFAT volume with too small cluster size can collapse unallocated memory. (appeared at R0.12)
- Fixed wrong object name can be returned when read directory at Unicode cfg. (appeared at R0.12)
- Fixed large file allocation/removing on the exFAT volume collapses allocation bitmap. (appeared at R0.12)
- Fixed some internal errors in f_expand() and f_lseek(). (appeared at R0.12)
This commit is contained in:
savelij13 committed 2025-09-11 10:16:39 +03:00
1 parent ea14f0f5de
commit e749807f86
33 files changed
+517 -302

No files matched your search

+1 -1
View File
@@ -59,7 +59,7 @@ FRESULT f_expand (
<li>The file has been opened in read-only mode.</li>
<li>Not allowable file size. (&gt;= 4GiB on FAT volume)</li>
</ul>
<p>When <tt class="arg">opt</tt> is 0, the function finds a contiguous data area and set it as suggested point for next allocation instead of allocating it to the file. The next cluster allocation is started at top of the contiguous area found by this function. Thus the write file is guaranteed be contiguous and no allocation delay until the size reaches that size at least unless any other operation to the volume with changes of FAT is performed.</p>
<p>When <tt class="arg">opt</tt> is 0, the function finds a contiguous data area and set it as suggested point for next allocation instead of allocating it to the file. The next cluster allocation is started at top of the contiguous area found by this function. Thus the write file is guaranteed be contiguous and no allocation delay until the size reaches that size at least unless any other changes to the volume is performed.</p>
<p>The contiguous file would have an advantage at time-critical read/write operations. It reduces some overheads in the file system and the storage media caused by random access due to fragmented file data. Especially, at the exFAT volume, any FAT access for the contiguous file is completely eliminated and storage media will be accessed sequentially.</p>
<p>Also the contiguous file data can be easily accessed directly via low-level disk functions but it is not recommended in consideration for future compatibility.</p>
</div>