similar to: ext3_readdir error

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Hi, yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have

Hi I got a strange error, happening on two of my ext3 partitions. What can be wrong? And why does e2fsck error out, instead of displaying an error message? Best regards keld fsck /dev/hda6 fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning... fsck.ext3 for device /dev/hda6 exited with signal 11. also From my dmesg: <1>general protection fault: e7a8 [#3] Modules linked in:

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is

Hi. IIRC, I had the same problem with 2.4.3 and ext2, I'm not sure if with the same directory entry, but at the time fsck fixed without any problems. I only know that the error again is with my Mozilla sources. The Mozilla sources are in another partition. I used lndir from my root fs to symlink everything and build it. At some point c++ segfaulted (happens a lot with my GCC 3.0), and I had

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

Hi all, i have the following configuration: RHAS 2.1 2.4.9-e.40enterprise #1 SMP (2 node cluster). ocfs-support-1.1.2-1 ocfs-tools-1.1.2-1 ocfs-2.4.9-e-enterprise-1.0.12-1 i followed the users guide to install and configure ocfs. During definition and formatting of ocfs-partitions the ocfstool crashed. Now restarting ocfstool fails with the following error: ocfstool Abnormal termination!

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hi, I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus the ext3-cvs.patch that Andrew Morton pointed me to for addressing and assertion failure. Since then I have been getting lots of errors like: May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927,

I'm trying to run e2fsck on a ~6TB filesystem which is about 90% full. We're doing backup to disk to this filesystem, and have a number of hard links (link counts up to 90). strace shows: write(1, "Pass 2: Checking ", 17) = 17 write(1, "directory", 9) = 9 write(1, " structure\n", 11) = 11 mmap(NULL, 91574272,

Hi, thank you so! much. Turning off avahi daemon was the solution! rapsberry instead of raspberry is a typo during porivision actually. Thank you again :) I will write an entry on my blog to make sure that does not happen again. One last time for google bots. IF you receive kinit: Cannot contact any KDC for realm while getting initial credentials make sure you don't run avahi However

Hi, i am really depressed at this moment. I set up an domain controller using samba4 and an raspberry pi. I can join the domain and everything works BUT kerberos has some strange problems resolving my raspberry hostname. First of all some information: Raspberry pi is DHCP Server and DNS-Server (BIND9). First of all the configurations: Code: /usr/local/samba/etc/smb.conf # Global

Hi, /etc/resolv.conf looks exactly like this: domain family.rapsberry.local search family.rapsberry.local nameserver 192.168.178.222 So to answer your question: yes the only Nameserver the raspberry has is itself. Greetings Am 2015-01-03 um 7:40 PM schrieb Rowland Penny: > On 03/01/15 16:31, Robert Hartmann wrote: >> Hi, >> >> i am really depressed at this moment. I set

Hello list I've been having the following error messages pop up in my kernel log: Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0, inode=827218527, rec_len=20275, name_len=73 Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670596: rec_len %% 4 != 0 -

Hi RedHat 7.2, ext3 on /, kernel 2.4.18p1. whilst updatedb was running, i had these messages appear... Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 - offset=0, inode=1651076143, rec_len=19527, name_len=85 Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory

Jul 25 01:41:21 big kernel: EXT3-fs error (device device-mapper(254,16)): ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 - offset=0, inode=538976266, rec_len=14637, name_len=49 Jul 25 01:42:53 big kernel: EXT3-fs error (device device-mapper(254,16)): ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 - offset=0, inode=538976266, rec_len=14637, name_len=49

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many

I'm trying to update my CentOS 5.6 boxes to 5.7, and on every single one of them yum is failing with a segmentation fault: the error happens when yum is checking the 'base' repository. [root at picard yum]# yum update Loaded plugins: downloadonly, fastestmirror, priorities Determining fastest mirrors * base: mirrors.ircam.fr * extras: mirrors.ircam.fr * updates:

Hi. I woke up this morning to find a ton of waiting emails complaining that some cron jobs on my system couldn't run because one of my filesystems (ext3 on software RAID 1) was suddenly mounted read-only. Always nice when you're away from the server due to travel. ;^> I investigated in the logs and found: 2007-08-02 04:02:25 kern.crit www kernel: EXT3-fs error (device md2):