Ext3-fs Error Device Sdb1 Ext3_readdir
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support
Ext3-fs Error Deleted Inode Referenced
AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web ext3 fs error ext3_journal_start_sb detected aborted journal Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help http://kb.fortinet.com/kb/documentLink.do?externalID=FD37499 [SOLVED] Linux - problem in repairing/recreating ext3 filesystem Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 3 of 3 Thread: Linux - problem in repairing/recreating ext3 filesystem Thread Tools Show Printable Version Subscribe to this Thread… https://ubuntuforums.org/showthread.php?t=2069528 Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October 11th, 2012 #1 gr@ss_h@pper View Profile View Forum Posts Private Message Spilled the Beans Join Date Nov 2009 Beans 14 Linux - problem in repairing/recreating ext3 filesystem Hi, This might not be the correct place to ask this question as it's more of a generic Linux filesystem question. But anyway as I am not in any other forum, i thought of asking the Ubunutu Family Ok. So I am on kernel 2.6.32.58-26 with MIPS arch. It's an embedded environment and I can't do desktop like experiments on this. mount shows: /dev/sda1 on /xxx type ext3 (rw,sync,relatime,errors=continue,data=ordered) On this partition /xxx some important binaries like kernel image and uboot etc resides. I am not totally sure who mounts it at boot up but it's unmountable on a running system. >umount /xxx umount: can't umount /xxx: Device or resource busy Now due to something, this filesystem on this partition got corrupted. Now filesystem operations are giving errors: root@YYY:~ >cd
here for a quick overview of the site Help Center Detailed answers to any questions you might http://unix.stackexchange.com/questions/92633/server-down-and-require-manual-fsck-i-saw-this-error-in-dmesg 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 https://bugs.launchpad.net/bugs/403026 with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, fs error 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 favorite 1 ext3-fs error (device 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 kernel: Linux version 2.6.32-358.
Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Expired Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: msp3k When: 2009-07-22 Completed: 2010-08-12 Target Distribution Baltix BOSS Juju Charms 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 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 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. Although this seems similar to a bug reported in 2007 here: http://marc.info/?l=linux-ext4&m=118067140512836&w=2 I was unable to reproduce the error with the original report's program and script. In fact, I have as yet been unable to reproduce the error at all. ProblemType: Bug Architecture: amd64 CurrentDmesg: [ 55.509463] NET: Registered protocol family 17 [ 60.212556] Installing knfsd