UBIFS do_writepage error

[Sungkyun]

Dear sir,

I'm using an i.mx6ull (SDK 2.0.0) with a NAND flash.

But, The following error occurs only on certain boards, and the file system is changed to read only.

It will be recovered upon reboot, but the same phenomenon will be repeated soon.

What's the cause?

UBIFS error (ubi0:0 pid 6): ubifs_scan: corrupt empty space at LEB 1718:112454
UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: corruption at LEB 1718:112454
UBIFS error (ubi0:0 pid 6): ubifs_scanned_corruption: first 8192 bytes from LEB 1718:112454
UBIFS error (ubi0:0 pid 6): ubifs_scan: LEB 1718 scanning failed
UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 2363 bytes in jhead 2, error -117
UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5304 of inode 37836, error -117

UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5315 of inode 37836, error -30
UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1199 bytes in jhead 2, error -30
UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5316 of inode 37836, error -30
UBIFS error (ubi0:0 pid 6): make_reservation: cannot reserve 1262 bytes in jhead 2, error -30
UBIFS error (ubi0:0 pid 6): do_writepage: cannot write page 5317 of inode 37836, error -30

Thanks.

Best Regards,

Sungkyun Ko

[Dhruvit]

Hi @Sungkyun,

This UBIFS error is reported many times, for certain reasons like the NAND driver or the HW is buggy.
When the flash regions have been erased but have never been written, UBIFS expects to see all 0xFFs there, and if it doesn't, it reports about corrupt space.

There is a possibility to switch to read-only mode to prevent further corruption due to corrupt space error.

For further debugging of the issue, we would recommend you get in touch with the MDT community.

Thanks & Regards,
Dhruvit.