similar to: Question about EXT3 error messages in /var/log/messages

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

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

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 ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

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, 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 all, Sorry for the repost. If I should be asking somewhere else please tell me where. I woke up a few days ago to find this on one of my machines. Below is hopefully the revelent output from dmesg and /var/log/messages. I have had this b4 but this is the first time I have been able to get any useful information from it. The machine usually locks and all I see is the assertion failure on

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,

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. 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

Hi, I am getting the following errors on /boot partition on a production server running 2.4.18 kernel. ------------- Aug 10 00:19:37 kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ------------- /boot is not readable at all and attempt to do an ls will return the same error.

Hello all, I am new to this list and hope that my mail is not OFF TOPIC. After looking around for 2 months now, to find a solution, I will try it here now. Now the scenario: I bought a new cool dell laptop: INSPIRON 8100, 512MB RAM, NVIDEA GeForce2Go 32MB, 30GB Hitachi hard disk and a DVD. I bought it with WinME preinstalled, because it wasn't possible to get it with linux nor without an

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

Can anyone give me a clue on how to find out more information from this type of error: Oct 17 05:01:08 ara kernel: EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #8945865: rec_len %% 4 != 0 - offset=0, inode=93580797, rec_len=5963, name_len=106 Oct 17 05:01:08 ara kernel: EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #8945869: rec_len is smaller

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

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

Hi all, I woke up this morning to find this on one of my machines. The machine is still running but the load according to top is over 13 yet I see no processes actually loading the machine. The only running process is top itself. Below is hopefully the revelent output from dmesg and /var/log/messages. I have had this b4 but this is the first time I have been able to get any useful information

Hi! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

On 1/5/23 06:22, Rowland Penny via samba wrote: > > > On 05/01/2023 10:20, Zombie Ryushu via samba wrote: >> Does anyone know how to completely remove the Computer SID of a >> Demoted DC? As in, another DC has taken it's place, the system is >> down and offline, but if it rejoins, it will not get the SID entry it >> had before? >> > > >

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted