Ext2-fs Error Device Ram0 Ext2_check_page Bad Entry In Directory
| Forgot Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug585282 - ext2_check_page: bad entry in directory / ext2_readdir: bad page after large copy Summary: ext2_check_page: bad entry in directory / ext2_readdir: bad page after large ... Status: CLOSED INSUFFICIENT_DATA Aliases: None Product: Red Hat Enterprise Linux 5 Classification: Red Hat Component: kernel (Show other bugs) Sub Component: --- Storage Multiple Devices (MD) Device Mapper Core Crypt Multipath RAID Snapshots Other Storage Drivers Other File Systems GFS/GFS2 XFS ext* NFS CIFS AutoFS Other Networking Protocol sctp igmp/mld tcp udp arp/icmp IPv6 NIC Drivers Vlan Bonding Team Bridge OVS Tunnel IPSec/Crypto Netfilter PTP Misc Memory management Scheduler Power Management Process management Desktop Graphics Audio V4L fbdev USB Other Virtualization Xen ESX Hyper-V KVM Other Debugging/Tracing Kexec/kdump Utrace/Uprobe/Ptrace EDAC/HERM Oprofile Systemtap Locking/lockdep Other Platform Enablement Wireless Infiniband Crypto Security SELinux Audit TPM Key Management Other Other Version: 5.5 Hardware: x86_64 Linux Priority low Severity medium TargetMilestone: rc TargetRelease: --- Assigned To: Eric Sandeen QA Contact: Red Hat Kernel QE team Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2010-04-23 11:27 EDT by Doug Kelly Modified: 2011-05-05 15:35 EDT (History) CC List: 2 users (show) esandeen rwheeler See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2011-05-05 15:35:42 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use)
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 https://bugzilla.redhat.com/show_bug.cgi?id=585282 crops up monthly or 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 http://serverfault.com/questions/54643/ext2-fs-error-which-crops-up-monthly-or-sometimes-weekly to be very sporadic and 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
I recover my files? kung fu buntuJune 18th, 2009, 03:12 AMI got home from work and while using the computer I tried https://ubuntuforums.org/archive/index.php/t-1190470.html to copy one file from one HDD to another, but cp returned https://lists.ozlabs.org/pipermail/linuxppc-embedded/2008-July/030809.html an error telling me the system is read only. I try to ls the mountpoint contents as root and I get a "total 0". But by typing "ls /mntpoint/some_dir" I can navigate through the subdirectories and access files. Advised by some people I force a fsck and ext2-fs error reboot the system. This is the log file: Log of fsck -C -R -A -a -f Wed Jun 17 20:16:33 2009 fsck 1.41.0 (10-Jul-2008) /dev/sdc1: Superblock has an invalid ext3 journal (inode 8). CLEARED. *** ext3 journal has been deleted - filesystem is now ext2 only *** /dev/sdc1: Resize inode not valid. /dev/sdc1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without ext2-fs error device -a or -p options) /dev/sdb1: 66960/78464 files (24.4% non-contiguous), 59582858/80325000 blocks /dev/sdb2: 11/40800 files (0.0% non-contiguous), 50657/41766991 blocks fsck died with exit status 4 Wed Jun 17 20:25:26 2009 ---------------- When I try to run e2fs, I get: #e2fsck /dev/sdc1 e2fsck 1.41.3 (12-Oct-2008) Resize inode not valid. Recreate
by: [ date ] [ thread ] [ subject ] [ author ] Hi All, I have built a 2.6.14 image and Ramdisk for my board witch has a ppc 8349 processor with 1G DDR. The system works file if I build it without highmem support but if I try to add highmem support to the system, witch I need in order to expand my memory to 2G, I get the following error: EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #2: directory entry across blocks - offset=0, inode=2147614725, rec_len=1152, name_len=8 This is my console output: ==== Booting kernel ==== ## Booting image at 00200000 ... Image Name: Linux-2.6.14.7-saline Image Type: PowerPC Linux Kernel Image (grip compressed) Data Size: 1658344 Bytes = 1.6 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAM Disk Image at 01000000 ... Image Name: Corrigent_ignited_fess Image Type: PowerPC Linux RAM Disk Image (grip compressed) Data Size: 13721548 Bytes = 13.1 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Ramdisk to 0b2ea000, end 0bffffcc ... OK Linux version 2.6.14.7-saline (nadavs at nadavs_l.corrigent.com) (gcc version 3.4.4 (Wind River Linux)) #50 PREEMPT Sun Jul 13 11:04:30 IDT 2008 Built 1 zonelists Kernel command line: root=/dev/ram0 rw ramdisk_size=300000 mem=1008M ip=192.168.10.50:192.168.10.1:192.168.10.1:255.255.255.0:SBC8349:eth0:of f console=ttyS1,115200,115200 debug_flag=no msm_standalone=no oper_mode=normal bootdir=msm_images vlan= sd= LTT : ltt-base init IPIC (128 IRQ sources, 8 External IRQs) at fe000700 PID hash table entries: 4096 (order: 12, 65536 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1005368k available (2612k kernel code, 960k data, 124k init, 114688k highmem) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 checking if image is initramfs...softlockup thread 0 started up. it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 13399k freed NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 0 of device 0000:00:00.0 PCI: Cannot allocate res