Ext2-fs Error Ext2_readdir Bad Page In

Cisco Bug: CSCuy48159 - CSR1k bootflash: spontaneous corruption Last Modified May 27, 2016 Product Cisco Cloud Services Router 1000V Series Known Affected Releases 15.5(1)S0.9 Description (partial) Symptom: The bootflash on a CSR may become corrupted without any intervention. The following errors are typical of the problem: %IOSXE-2-PLATFORM:kernel: EXT2-fs error (device sda1): ext2_readdir: bad page in #2 %IOSXE-2-PLATFORM:kernel: EXT2-fs error (device sda1): ext2_readdir: bad page in #2 %IOSXE-2-PLATFORM:kernel: EXT2-fs error (device sda1): ext2_readdir: bad page in #2 %IOSXE-2-PLATFORM:kernel: EXT2-fs error (device sda1): ext2_readdir: bad page in #2 Conditions: N/A View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability Trust and Transparency Center The Next Wave of The Internet Our People Careers Search Jobs Life at Cisco Programs Cisco Designated VIP Program Cisco Powered Financing Options Contacts Feedback Help Site Map Terms & Conditions PrivacyPrivacy Statement CookiesCooki

| 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 https://quickview.cloudapps.cisco.com/quickview/bug/CSCuy48159 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: https://bugzilla.redhat.com/show_bug.cgi?id=585282 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) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Doug Kelly 2010-04-23 11:27:29 EDT Description of problem: It appears that ext4 is showing signs of a corrupt FS after a rather large series of file copy operations. Right now, I'm in the process of moving roughly 5 or 6TB of data with an extremely large number of small files (~1kb) to an ext4 fs using rsync, and after about 3TB were copied, the filesystem began showing unusual errors, as shown by my syslog output. This seemed notable since the filesystem

HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware Hard Drive Failing? User Name http://www.linuxquestions.org/questions/linux-hardware-18/hard-drive-failing-505622/ Remember Me? Password Linux - Hardware This forum is for Hardware issues. https://ubuntuforums.org/archive/index.php/t-1190470.html Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? 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 ext2-fs error newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple 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 ext2-fs error ext2_readdir 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 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. Page 1 of 2 1 2 > Search this Thread 11-28-2006, 01:49 PM #1 keysorsoze Member Reg

I recover my files? kung fu buntuJune 18th, 2009, 03:12 AMI got home from work and while using the computer I tried to copy one file from one HDD to another, but cp returned 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 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 -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? Isn't this destructive? I would like to be able to recover all I can before I start "fixing" the disk. I also tried using different superblocks but I always get this message. I tried mounting read-only but it didn't work. # mount -o ro /dev/sdc1 /hdd_a_917GB/ # ls /hdd_a_917GB/ [3786.593656] EXT2-fs error (device sdc1): ext2_readdir: bad page in #2 ls: reading directory /hdd_a_917GB/: Input/output error (I tried accessing a known directory on my disk) # ls /hdd_a_917GB/some_dir/ [3854.013562] EXT2-fs error (device sdc1): ext2_check_page: bad entry in directory #2 : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ls: cannot access /hdd_a_917GB/some_dir/: No such file or directory If I try to use debugfs to get any information... # debugfs -c -s 214990848 -b 4096 /dev/sdc1 debugfs 1.41.3 (12-Oct-2008) /dev/sdc1: catastrophic mode - not reading inode or group bitmaps debugfs: ls / /: EXT2 directory corrupted debugfs:It doesn't matter if I pass the a superblock and block size, or not. How can I recover my files before doing destructive actions with fsck? And what are the implications of each possible answer to the question: Resize inode not valid. Recreate? BTW, I also ran smartctl -t short /dev/sdc and I got no errors. kung fu buntuJune 18th, 2009, 09:47 PM*bumpy* (sorry but this is really heart breaking :() bodhi.zazenJune 18th, 2009, 09: