We observe sometimes a file system corruption on the eMMC that we are not able to explain. Once it happened, either on rootfs or on data partition, the system is still working but affected files cannot be accessed as input / output error appears when we try to.
The output 'fsck' the command is as following :
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sdc2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'bluetooth' in /var/lib (4103) has deleted/unused inode 16391. Clear? no
Entry 'bluetooth' in /var/lib (4103) has an incorrect filetype (was 2, should be 0).
Entry 'dropbear' in /etc (8193) has deleted/unused inode 16390. Clear? no
Entry 'dropbear' in /etc (8193) has an incorrect filetype (was 2, should be 0).
Entry 'random-seed' in /etc (8193) has deleted/unused inode 8243. Clear? no
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -36700 -65798 -(66561--66562)
Inode bitmap differences: -8243 -(16390--16392) -16394
Directories count wrong for group #8 (6, counted=3).
/dev/sdc2: ********** WARNING: Filesystem still has errors **********
/dev/sdc2: 941/32768 files (17.3% non-contiguous), 58432/131072 blocks
Our system configuration :
- eMMC Micron in MCP package (MT29PZZZ4D4BKESK-18)
- Freescale BSP 3.14.52
Are there any known issues on that topic? Can mistake be on driver side?
For now, only way to fix it is formatting corrupted partition. Is there any other workaround which would fix file system without formatting (keeping data alive)?
Thank you for your help,