Ext2-fs Error Ext2_check_page Bad Entry In Directory

it enabled. Please turn JavaScript back on and reload this page.More questions in QorIQ Processing Platforms Where is this place located?NXP CommunityAll PlacesQorIQ Processing PlatformsLog in to create and rate content, and to follow, bookmark, and share content with other members.AnsweredAssumed AnsweredError when loading the fsl-image-virt image on the t1040 RDBQuestion asked by Juan Rodrigo on Sep 7, 2015Latest reply on Sep 10, 2015 by Juan Rodrigo Like • Show 1 Like1 Comment • 2It is required kvm-qemu to be available on a linux OS running on the T1040 RDB. So a fsl-image-virt image was created following SDK Technical Documentation. We deploy the image using the following commands:=>tftp 1000000 < uImage_name>=>tftp 2000000 fsl-image-core-.ext2.gz.u-boot=>tftp c00000 =>bootm 1000000 2000000 c00000And we get the following errors:RAMDISK: gzip image found at block 0VFS: Mounted root (ext2 filesystem) on device 1:0.devtmpfs: mountedFreeing unused kernel memory: 284K (c0871000 - c08b8000)EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #3889: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #3734: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b #1Call Trace:[e7083e80] [c0006f50] show_stack+0x40/0x150 (unreliable)[e7083ec0] [c06a186c] dump_stack+0x78/0xa0[e7083ed0] [c069fbac] panic+0xd8/0x1fc[e7083f20] [c000295c] kernel_init+0x16c/0x170[e7083f40] [c000fe0c] ret_from_kernel_thread+0x5c/0x64Rebooting in 180 seconds..How can we solve this?Thanks in advance.Yiping Wang Sep 9, 2015 1:59 AMCorrect AnswerHello Juan Rodrigo,Please download the filesystem at 4000000.Please refer to the following definition in include/configs/T104xRDB.h, the command line is allocated backward from 64M, if the ramdiskaddr starts at 32M, fsl-image-virt rootfs image is larger than 32M(about 44M), the command line data will be written in the middle of it, which causes the rootfs filesystem corrupted, so you will get filesystem setting up erro

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Ext2-fs error which crops up monthly or https://community.nxp.com/thread/373396 sometimes weekly up vote 2 down vote favorite 1 I have an extremely strange error message which causes a complete system crash and remount of the filesystem as read-only. It all started ages ago when I installed a dodgy $2 ebay PCI modem and there were kernel panics showing up monthly and the output was huge. A new hard disk and a dist-upgrade later I have gotten the error to be very sporadic and http://serverfault.com/questions/54643/ext2-fs-error-which-crops-up-monthly-or-sometimes-weekly a lot smaller in terms of what is actually printed. (it's still rubbish to me - even after thorough googling ) This system when booted into Debian has been 'cursed' I was thinking about trashing the computer and getting a new one... but because it is only a Linux problem it must be software!! Basically here it is (I post now because I crashed today but also yesterday): EXT2-fs error (device hda1): ext2_check_page: bad entry in directory #5898285: rec_len is smaller than minimal - offset=0, inode=5898285, rec_len=8, name_len=1 Remounting filesystem read-only What is going on? I then have to pull the power out, reboot, fsck -y, reboot and then that usually settles it for a while. If this could be figured out I would be so happy. Thanks in advance for any light you guys can shed on this matter. --EDIT: Now running updatedb causes this error every time (well twice) and that means it's reproducible and trackable! (now just to fix it...) Is it time for a new computer? --EDIT: resize2fs /dev/hda1 says it's already the correct amount of blocks long and badblocks doesn't return anything (is it not meant to?) --EDIT: Is it possible something is corrupting all my new disks? A hardware problem - someone said it might be the disk controller, or a bios option - i

Tags Search LQ Wiki Search Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Server bad entry in directory unaligned directory entry User Name http://www.linuxquestions.org/questions/linux-server-73/bad-entry-in-directory-unaligned-directory-entry-872361/ Remember Me? Password Linux - Server This forum is for the discussion of Linux http://www.securiteam.com/mirrors/projects.info-pull.com/mokb/MOKB-12-11-2006.html Software used in a server related context. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple ext2-fs error and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem ext2-fs error ext2_check_page logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 04-01-2011, 07:15 AM #1 rjo98 Senior Member Registered: Jun 2009 Location: US Distribution: RHEL, CentOS Posts: 1,664 Rep: bad entry in directory unaligned directory entry I have the following error on one of my servers. Is there a way to tell which directory is exactly having the problem? if there is, if i delete that directory, will that resolve the problem or no? kernel: EXT2-fs error (device md(9,0)): ext2_check_page

operation is being done on a crafted fs stream. Author/Contributor: LMH References: fsfuzzer for Linux Proof of concept or exploit: The following ext2 filesystem image can be used to reproduce the bug: MOKB-12-11-2006.img.bz2 Use a loopback device to mount it: bunzip2 MOKB-12-11-2006.img.bz2 && mount -t ext2 -o loop MOKB-12-11-2006.img /media/test Debugging information: The bug has been found using the Linux version of fsfuzzer on a Fedora Core 6 installation, with up to date packages as of 11-11-2006. A read operation is necessary to trigger the bug. The architecture used to conduct the tests is IA32/x86, SMP enabled. [root@fedoravm ~]# uname -a Linux fedoravm 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=24576, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=28672, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=32768, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=36864, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=40960, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=45056, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=49152, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=53248, inode=0, rec_len=0, name_len=0 EXT2-fs error (device loop1): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal