Unable to return from fds_gc(), stuck in infinite loop.

[Jagadeep Ram]

There is a bug in fds.c file, Please go through the below code snippet.

ret_code = fds_record_update(&desc, record_id);
if (ret_code == FDS_ERR_NO_SPACE_IN_FLASH)
{
            ret_code = fds_gc();
            ERROR_CHECK(ret_code);
            ret_code = fds_record_update(&desc, record_id);
 }

I do not return from fds_gc(), execution stays there for infinite. 

More information:

1) #define FDS_VIRTUAL_PAGES 30

2) #define FDS_VIRTUAL_PAGE_SIZE (1024)

3) Initialization is successful and able to write, update and read several records.

4) SDK version: nRF_SDK_15.2.0

The problem occurs when record_update is failed with FDS_ERR_NO_SPACE_IN_FLASH and followed by garbage collection function fds_gc().

According to me, a library function has to return an error code if something is wrong, but not locked in an infinite loop. This is a serious bug.

Please help me as I am stuck in the crucial phase of our development.

Regards,

Jagadeep

[ThierryC]

Hello,

I experienced a similar issue as Jagadeep Ram. It's not when I call fds_gc() on my case, but I got stuck on the same loop, where queue_has_next() return true, but FDS_OP in NONE and never get out of the loop !

About Kenneth suggestion to check fs_sys_event_handler(), I don't understand it. Is this function still called in SDK 15.2 ? I was thinking it was part of fstorage module.

On SDK15, on_operation_failure() is called inside nrf_fstorage_sd module and never hit on my case.

[Kenneth]

Can you provide an example we may run here to recreate it?

Best regards,
Kenneth

[mathiasvanbelle]

i see the same problem. How do i fixes this?

[Bevin]

Hi Kenneth

I also met the issue that fds_gc() would be stuck in SDK 15.3.0_59ac345.

Would it be possible for you to tell me if this problem has been solved or not?

Look forward to hearing from you soon.

Sincerely

Bevin 

[GT]

Hi Nordic team,

Is there any root cause for this issue? Is this confirmed as a bug in SDK?

Regards,

GT