Hmm, you are correct, it looks like we do not expose the OS_FileSysStatVolume_Impl info via a public API currently.

I can easily implement one as long as folks are in agreement that it is a reasonable solution. The structure currently is defined as:

typedef struct
{
    size_t            block_size;
    osal_blockcount_t total_blocks;
    osal_blockcount_t blocks_free;
} OS_statvfs_t;

Prototype would be:

int32 OS_FileSysStatVolume(const char *path, OS_statvfs_t *statbuf);

Filesystem code has traditionally used strings/pathnames to identify objects so this is consistent with other filesystem calls, as opposed to using an osal_id_t to identify the filesystem (which would be more like the rest of OSAL).

OS_fsBlocksFree returns a 32-bit value, but OS_statvfs_t.blocks_free is 64 bit #573

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions