Ext3-fs Error Htree_dirblock_to_tree
Contents |
bad entry in directory" error Date: Thu, 02 Aug 2007 09:01:34 -0700 Hi. I woke up this morning to find a ton of waiting emails complaining that some cron jobs ext4-fs error htree_dirblock_to_tree bad entry in directory on my system couldn't run because one of my filesystems (ext3 on
Ext4 Fs Error Rec_len Is Smaller Than Minimal
software RAID 1) was suddenly mounted read-only. Always nice when you're away from the server due to travel. rec_len is smaller than minimal offset=0, inode=0, rec_len=0, name_len=0 ;^> I investigated in the logs and found: 2007-08-02 04:02:25 kern.crit www kernel: EXT3-fs error (device md2): htree_dirblock_to_tree: bad entry in directory #3616894: rec_len is too small for name_len - offset=103576, ext3_add_entry: bad entry in directory inode=3619715, rec_len=12, name_len=132 2007-08-02 04:02:25 kern.err www kernel: Aborting journal on device md2. 2007-08-02 04:02:25 kern.crit www kernel: ext3_abort called. 2007-08-02 04:02:25 kern.crit www kernel: EXT3-fs error (device md2): ext3_journal_start_sb: Detected aborted journal 2007-08-02 04:02:25 kern.crit www kernel: Remounting filesystem read-only I unmounted the filesystem and ran fsck, but though it detected that the filesystem had errors, it didn't report any
Directory Hole Found
findings during the check: fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) /dev/md2: recovering journal /dev/md2 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/md2: 200231/5248992 files (1.4% non-contiguous), 1563304/10492432 blocks I remounted the filesystem and all *seems* to be okay now. I was curious what "directory #3616894" (inode 3619715) was, so I did 'find / -inum 3619715 -exec ls -dioF {} \;', but the output showed that that was a non-directory file created and last modified in 2004. How could this be? And what would cause an error like the above? Am I out of the woods now, or is there more checking of some kind that I should do to make sure this isn't going to be happening again? Thank you for your time! -- Dan Harkless http://harkless.org/dan/ Follow-Ups: Re: "htree_dirblock_to_tree: bad entry in directory" error From: Andreas Dilger [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
here for a quick overview of the site Help Center Detailed answers to any questions you fsck 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 Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of https://www.redhat.com/archives/ext3-users/2007-August/msg00003.html Linux, FreeBSD and other Un*x-like operating systems. 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 Server down and require manual fsck. I saw this error in dmesg up vote 0 down vote http://unix.stackexchange.com/questions/92633/server-down-and-require-manual-fsck-i-saw-this-error-in-dmesg favorite 1 I saw this in dmesg. What does it mean? EXT4-fs error (device sdb1): htree_dirblock_to_tree: bad entry in directory #763 3575: rec_len is smaller than minimal - block=30429885offset=0(671744), inode=0, rec_len=0, name_len=0 How in the earth this happen? Is this because SDB is bad? This is what /var/messages say Sep 26 17:15:40 host pure-ftpd: (?@175.44.11.232) [INFO] New connection from 175.44.11.232 Sep 26 17:15:40 host pure-ftpd: (?@27.150.198.182) [INFO] Logout. Sep 26 17:15:41 host pure-ftpd: (?@216.244.84.165) [WARNING] Authentication failed for user [solarromancecom] Sep 26 17:15:41 host pure-ftpd: (?@216.244.84.165) [INFO] Logout. Sep 26 17:15:41 host pure-ftpd: (?@27.150.198.182) [INFO] New connection from 27.150.198.182 Sep 26 17:15:41 host pure-ftpd: (?@216.244.84.165) [INFO] New connection from 216.244.84.165 Sep 26 17:15:43 host pure-ftpd: (?@202.100.206.34) [WARNING] Authentication failed for user [admSep 27 04:17:49 host kernel: imklog 5.8.10, log source = /proc/kmsg started. Sep 27 04:17:49 host rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1708" x-info="http://www.rsyslog.com"] start Sep 27 04:17:49 host kernel: Initializing cgroup subsys cpuset Sep 27 04:17:49 host kernel: Initializing cgroup subsys cpu Sep 27 04:17:49 host k
Start here for a quick overview of the site Help Center Detailed answers to any questions you might http://serverfault.com/questions/449537/how-can-i-track-down-the-cause-of-ext3-filesystem-corruption have Meta Discuss the workings and policies of this site About https://www.novell.com/support/kb/doc.php?id=3554036 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; fs error 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 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 bad entry in CentOS 5.8 virtual machines. In the past two weeks we have had five incidents of virtual 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 #216
Favorite Rating: EXT3 file-system error "bad entry in directory"This document (3554036) is provided subject to the disclaimer at the end of this document. Environment Novell Linux Desktop 9Novell Open Enterprise Server 1 (OES1) Support Pack 2 LinuxNovell Open Enterprise Server 2 (Linux based)Novell openSUSE 10.XNovell SUSE Linux Desktop 1.0Novell SUSE Linux Enterprise Desktop 10Novell SUSE Linux Enterprise Server 10Novell SUSE Linux Enterprise Server 9 Situation At reboot, or mount of an EXT3 file-system, an error similar to the one below is seen:EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #5556142: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 Resolution This error is caused by a file that has been marked as a directory. This is a non-fatal error and can be fixed by removing the file in question.Mount the file-system in questionLocate the file that has been corrupted. The file's inode is the number after "bad entry in directory" Using the example error code the file would be found by typingfind /MOUNT_POINT-inum 5556142Delete the file identified in step twoUmount the file-systemCheck the disk, and check for errors.fsck/dev/PHYSICAL_DEVICERepeat step 5. If no errors, the file-system is clean. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:3554036Creation Date:05-JAN-08Modified Date:30-APR-12SUSESUSE Linux Enterprise DesktopSUSE Linux Enterprise Real Time ExtensionSUSE Linux Enterprise Server Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS