RTEMS | cpukit: Move FatFs core to cpukit/contrib (!1071)

SHIVAM DEOLANKAR (@D3athSkulll) gitlab at rtems.org
Sun May 24 15:31:11 UTC 2026




SHIVAM DEOLANKAR commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_150948


I investigated this issue in main and on my MR.

The failing assertion is:` cluster_size == stat_buff.st_blksize` 

This test is passing for a FAT cluster size 512 byte, but fails when formatting with cluster size 4096 byte. This is because `stat_buff.st_blksize`  still reports 512 byte.

>From the POSIX definition, st_blksize is the preferred I/O block size and may not necessarily correspond to FAT allocation cluster size. This means, st_blksize is not the correct interface for validating FAT cluster size semantics

In short, the assertion seems to be overly strict rather than a filesystem failure. A solution could be to relax the assertion to `stat_buff.st_blksize > 0`  or else remove it entirely.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_150948
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260524/449cdb01/attachment.htm>


More information about the bugs mailing list