Ext3-fs Error Device Dm-0 Htree_dirblock_to_tree
Contents |
Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Expired Undecided Unassigned Edit You need ext4-fs error htree_dirblock_to_tree bad entry in directory to log in to change this bug's status. Affecting: linux
Ext4 Fs Error Rec_len Is Smaller Than Minimal
(Ubuntu) Filed here by: msp3k When: 2009-07-22 Completed: 2010-08-12 Target Distribution Baltix BOSS Juju Charms rec_len is smaller than minimal offset=0, inode=0, rec_len=0, name_len=0 Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance
Ext3_add_entry: Bad Entry In Directory
Expired Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description We lost storage on three of our servers to (what I believe to be) a bug in the directory hole found ext3 kernel filesystem driver. Syslog shows the following: Jul 14 01:45:04 home kernel: [981637.615765] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #217677844: rec_len % 4 != 0 - offset=0, inode=3672412761, rec_len=39053, name_len=147 Jul 14 01:45:04 home kernel: [981637.653163] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #216096885: rec_len % 4 != 0 - offset=0, inode=1193450085, rec_len=48787, name_len=24 Jul 14 01:45:05 home kernel: [981637.821762] EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #216105487: directory entry across blocks - offset=0, inode=884141655, rec_len=41788, name_len=189 This error repeats, growing in length as other inodes are added to the list of errors. Out of 8 drives formatted ext3, the only drives affected were very large RAID arrays (12TB and 16TB in size). Three of five RAID arrays suffered permanent dammage and could not be repaired. It is unknown if the size of the drive is a contributing factor.
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat
Fsck
Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data https://bugs.launchpad.net/bugs/403026 Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting https://access.redhat.com/solutions/67695 Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Con
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://serverfault.com/questions/449537/how-can-i-track-down-the-cause-of-ext3-filesystem-corruption 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: fs error Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How can I track down the cause of ext3 filesystem corruption? up vote 4 down vote favorite 1 We have a VMware vSphere 5 environment running CentOS 5.8 virtual machines. In the past two weeks we have had five incidents of virtual bad entry in machines having a filesytem become corrupt, requiring an fsck to repair. Here is what we see in the logs: Nov 14 14:39:28 hostname kernel: EXT3-fs error (device dm-2): htree_dirblock_to_tree: bad entry in directory #2392098: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Nov 14 14:39:28 hostname kernel: Aborting journal on device dm-2. Nov 14 14:39:28 hostname kernel: __journal_remove_journal_head: freeing b_committed_data Nov 14 14:39:28 hostname last message repeated 4 times Nov 14 14:39:28 hostname kernel: ext3_abort called. Nov 14 14:39:28 hostname kernel: EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal Nov 14 14:39:28 hostname kernel: Remounting filesystem read-only Nov 14 14:39:28 hostname kernel: EXT3-fs error (device dm-2): htree_dirblock_to_tree: bad entry in directory #2392099: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Nov 14 14:31:17 hostname ntpd[3041]: synchronized to 194.238.48.2, stratum 2 Nov 14 15:00:40 hostname kernel: EXT3-fs error (device dm-2): htree_dirblock_to_tree: bad entry in directory #2162743: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Nov 14 15:13:17 hostname kernel: __journal_remove_journal_head: freeing b_committed_data The problem seems to happen while we are rsync'ing application data from another serve