This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM1808, kernel 3.17.0, several mmc / ext4 errors

Dear all,

i am running linux, mainline kernel 3.17.0 on

[root@test ~]# cat /proc/cpuinfo 
processor	: 0
model name	: ARM926EJ-S rev 5 (v5l)
Features	: swp half thumb fastmult edsp java 
CPU implementer	: 0x41
CPU architecture: 5TEJ
CPU variant	: 0x0
CPU part	: 0x926
CPU revision	: 5
[root@test ~]# cat /proc/version
Linux version 3.17.0 (angelo@test) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #204 PREEMPT Tue Nov 11 15:05:16 CET 2014

I have finally this new kernel up and running (moved from 3.5.1), but i am noticing several mmc ext4 errors, as

InfoGeneral:RegistrationMng hearth beat log (nothing to do since 10 seconds).
EXT4-fs (mmcblk0p1): error count since last fsck: 24
EXT4-fs (mmcblk0p1): initial error at time 946685647: ext4_lookup:1448: inode 130311
EXT4-fs (mmcblk0p1): last error at time 946687362: empty_dir:2539: inode 11: block 8658

Never seen errors like those in kernel 3.5.1. I am considering them related to this kernel upgrade.  If any idea on what direction to investigate, just let me know.



  • Hi Angelo,

    Do you have any filesystem content in "mmcblk0p1" ?

    Actually we keep the filesystem in "mmcblk0p2" right ?

    Have you tried "ext3" fs on this ?

    Did you compare the both kernel versions of ext4 code and linux kernel release notes related to ext4 ?

  • Hi

    i have /dev/mmcblk0p1 formatted ext4, and no other partitions

    i use mkfs.ext4 to re-format.

    Now i did this test:

    1) formatted the microsd as ext4

    2) written several files

    3) unmounted

    4) checked fsck.ex4

    [root@test media]# umount  mmcsd0p1/
    VFS: Busy inodes after unmount of mmcblk0p1. Self-destruct in 5 seconds.  Have a nice day...
    [root@test media]# fsck.ext4 /dev/mmcblk0p1 
    e2fsck 1.42.4 (12-June-2012)
    /dev/mmcblk0p1: clean, 88/488640 files, 122803/1952881 blocks
    
    

    5) mounted again

    [root@test media]# mount /dev/mmcblk0p1 /media/mmcsd0p1/
    EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
    EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
    EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
    

    6) removed a folder, and here comes all the errors:

    [root@test mmcsd0p1]# rm -r folder/
    EXT4-fs error (device mmcblk0p1): ext4_lookup:1441: inode #260611: comm rm: 'streams' linked to parent dir
    rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260611) - no `.' or `..'
    folder/set_1/configuration/streams/streams': Input/output error
    EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260618) - no `.' or `..'
    EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260615) - no `.' or `..'
    EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260616) - no `.' or `..'
    EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260617: comm rm: deleted inode referenced: 260611
    rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260617) - no `.' or `..'
    folder/set_1/firmware/streams': Input/output error
    EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260619: comm rm: deleted inode referenced: 260611
    rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir #260619) - no `.' or `..'
    folder/set_1/schedule/streams': Input/output error
    EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260610: comm rm: deleted inode referenced: 260611
    rm: can't stat 'folder/downloads/streams': Input/output error
    rm: can't remove 'folder/downloads': Directory not empty
    rm: can't remove 'folder': Directory not empty
    [root@test mmcsd0p1]# 

    Will try now with ext3