Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

stability of ext2 file system on SD Card

Other Parts Discussed in Thread: AM1808, DA8XX

I'm planning to put root file system on ext2 file system on the SD card of our OMAP L138 based system. 

(I'm limited to ext2 system I also placed uImage on the same partition and u-boot is only able to read ext2 or FAT partition on SD card).

But I'm observing that file system gets corrpted if the device is power cycled.  During the reboot, I observe:

EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 6161
EXT2-fs (mmcblk0p2): error: remounting filesystem read-only
/etc/rcS.d/S03udev: line 50: can't create /tmp/uname: Input/output error
EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 6161
EXT2-fs (mmcblk0p2): error: remounting filesystem read-only
touch: /tmp/uname: Input/output error

 

What kind of file system people uses in embedded Linux system which can survive the powe cycling?

 

 

 

 

  • Hello,

    The ext2 filesystem does not respond well to power cycles without it being unmounted first. I recommend you use ext3 instead which is a journaled filesystem, it is more resilient in these scenarios. Note that it's always good practice to umount a filesystem before power cycling regardless.

    Regards, Niclas

  • Hi Niclas,

    Having seen your response, I tried changing my sd card file system to ext3. To my surprise, u-boot didn't have any problem booting it. I guess unless you mount the file system and just treat it as read only file system, ext3 is as compatible as ext2. Without much of work, now my SD card is reporting no corruption while going through multiple power cycling.

    Thanks!

  • Hiroto-San,

    You would need a journalling filesystem to survive multiple power cycle or unclean mount of storage devices.

    EXT3, EXT4 are some of the jounaling filesystems available under linux.

     

    regards

    swami

  • Hi, 

    I am also having similar issue

    I am using AM1808 processor(Linux 2.6.32). It has 1 USB Host + 1 mini USB feature is available.

    Before mini USB, the main Host USB is working fine in my AM1808 I can see the files in my Pen-drive.

    When i added mini USB driver, both are working some time, after testing simultaneously my USB Host Pen-drive is not showing any files in my Qt application.

    And i have cross checked in Console also. Please find the status of my USB + mini-USB.

    USB HOST(Pen-Drive) CONNECT:-

    root@am180x-evm:~#

    usb 1-1: new full speed USB device using ohci and address 6

    scsi 4:0:0:0: Direct-Access Kingston DataTraveler G3 1.00 PQ: 0 ANSI: 4

    sd 4:0:0:0: Attached scsi generic sg0 type 0
    mnsd 4:0:0:0: [sda] 30233588 512-byte logical blocks: (15.4 GB/14.4 GiB)
    sd 4:0:0:0: [sda] Write Protect is off
    sd 4:0:0:0: [sda] Assuming drive cache: write through
    esd 4:0:0:0: [sda] Assuming drive cache: write through
    sda: sda1
    sd 4:0:0:0: [sda] Assuming drive cache: write through
    sd 4:0:0:0: [sda] Attached SCSI removable disk

    FAT: invalid media value (0x00)
    VFS: Can't find a valid FAT filesystem on dev sda.

     

    USB HOST(Pen-Drive) DISCONNECT:-

    usb 1-1: USB disconnect, address 2

    mini USB HOST CONNECT:-

    g_file_storage gadget: high speed config #1

    mini USB HOST DISCONNECT:-

    da8xx_interrupt 513: Unhandled USB IRQ 00090000
    Simultaneous Exercise
    Mini usb is still working
    But main HOST (Pendrive) is not working: the message shows continusely.

    usb 1-1: new full speed USB device using ohci and address 5
    scsi4 : usb-storage 1-1:1.0
    scsi 4:0:0:0: Direct-Access Kingston DataTraveler G3 1.00 PQ: 0 ANSI: 4
    sd 4:0:0:0: Attached scsi generic sg0 type 0
    sd 4:0:0:0: [sda] 30233588 512-byte logical blocks: (15.4 GB/14.4 GiB)
    sd 4:0:0:0: [sda] Write Protect is off
    sd 4:0:0:0: [sda] Assuming drive cache: write through
    sd 4:0:0:0: [sda] Assuming drive cache: write through
    sda: sda1
    sd 4:0:0:0: [sda] Assuming drive cache: write through
    sd 4:0:0:0: [sda] Attached SCSI removable disk
    FAT: invalid media value (0x00)
    VFS: Can't find a valid FAT filesystem on dev sda.
    EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 161612
    EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 161612
    EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 161612
    EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 161612
    EXT2-fs (mmcblk0p2): error: ext2_lookup: deleted inode referenced: 161612

    Please tell me any body known my relaed issue

    Thanks,

    Fracs