I am using linux kernel 2.6.10

after some time one of the file system is becoming read only.

Here is the kernel dump

Freeing unused kernel memory: 160k init
kjournald starting. Commit interval 5 seconds
EXT3-fs warning (device hda1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device hda1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on hda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
eth1: no IPv6 routers present
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.


EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16914: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Aborting journal on device hda1.
ext3_abort called.
EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16920: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16914: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16920: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16914: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs error (device hda1): ext3_readdir: bad entry in directory #16920: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0



Please throw lights on this

File system info
root@santhosh:~# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw,noatime)
proc on /proc type proc (rw,nodiratime)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/root on /dev/.static/dev type jffs2 (rw,noatime)
none on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /home type ext3 (ro,data=ordered)
/dev/hda2 on /home/logs type ext3 (rw,data=ordered)
/dev/hda3 on /home/config type ext3 (rw,data=ordered)
/dev/mtdblock4 on /upgrade type jffs2 (rw,noatime)



root@santhosh:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/root / auto defaults,errors=remount-ro 0 0
none /proc proc noauto 0 0
none /sys sysfs noauto 0 0
none /dev/pts devpts noauto,gid=5,mode=620 0 0
none /dev/shm tmpfs noauto 0 0
/dev/hda1 /home ext3 defaults 1 2
/dev/hda2 /home/logs ext3 defaults 1 2
/dev/hda3 /home/config ext3 defaults 1 2
/dev/mtdblock4 /upgrade jffs2 defaults 0 0


root@santhosh:~# cat /etc/mtab
rootfs / rootfs rw 0 0
/dev/root / jffs2 rw,noatime 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
tmpfs /tmp tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/root /dev/.static/dev jffs2 rw,noatime 0 0
none /dev tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
/dev/hda1 /home ext3 ro,data=ordered 0 0
/dev/hda2 /home/logs ext3 rw,data=ordered 0 0
/dev/hda3 /home/config ext3 rw,data=ordered 0 0
/dev/mtdblock4 /upgrade jffs2 rw,noatime 0 0

root@santhosh:~# fdisk -l

Disk /dev/hda: 4110 MB, 4110188544 bytes
127 heads, 62 sectors/track, 1019 cylinders
Units = cylinders of 7874 * 512 = 4031488 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 962 3787363 83 Linux
/dev/hda2 963 1013 200787 83 Linux
/dev/hda3 1014 1019 23622 83 Linux

It told you it found errors and suggested you to fsck the partition a gazillion times.

I am using linux kernel 2.6.10 (from monta vista distribution)
One of the partition in our device which was formated with ext3 file system, was re mounted with readonly access after couple of months run.
It was working fine for couple of months.
After browsing I had found out that there is a bug in kernel.

I just wanted to know in which kernel version above bug is fixed. And where do i find the bug reference?


Our device will run for a year without any reboot, so we don't want device to encounter the same problem.
Running fsck in regular interval(say 3 months) is overhead for the system, also if we do fsck device will
stop recording in that duration.

In simple word we don't want to encounter above problem in the device.

It would be really appreciated if I get some hints to solve the issues.

Since you didn't state which bug you best search LXR (Linux Cross Reference) kernel source sites or manually diff kernel source versions or search common distribution bug trackers for hints.


Nothing points to a specific bug as far as I can see so it doesn't rule out problems with hardware, chipsets, kernel, drivers, distribution, release, memory, filesystem or user-driven system abuse. Some embedded systems vendors still favor the 2.4 kernel and non-journalling filesystems over anything 2.6 can offer...

here is the mail thread where same problem is discussed.
http://linux.derkeiler.com/Mailing-L...4-03/3033.html
http://linux.derkeiler.com/Mailing-L.../519index.html

http://www.cyberciti.biz/tips/linux-...read-only.html