similar to: EXT3-fs error (device ide0(3,9)): ext3_readdir

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.

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

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

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

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

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

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

[ Tried to check the archives but the website seems to be down or something ] On one of our installations, I am seeing messages such as: EXT3-fs warning (device ide0(3,9))): ext3_free_inode: bit already clearned for inode 14 Anybody know exactly what they mean? These would be on a 0.0.6a system. b.

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

Hi all. I have two hosts with drbd: kmod-drbd83-8.3.8-1.el5.centos drbd83-8.3.8-1.el5.centos and kernel (CentOS 5.7): 2.6.18-308.4.1.el5 After a recent upgrade of kernel I have had two sitiuations when my ext3 filesystem on /dev/drbd0 became read-only. I've checked disks with smartctl -t long, they are ok. There are no messages with disks problems in /var/log/messages | dmesg. I've made

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

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):

I recently set up a new system to run backuppc on centOS 5 with the archive stored on a raid1 of 750 gig SATA drives created with 3 members with one specified as "missing". Once a week I add the 3rd partition, let it sync, then remove it. I've had a similar system working for a long time using a firewire drive as the 3rd member, so I don't think the raid setup is the cause

The patch below contains the following cleanups: - make some needlessly global code static - super.c: remove the unused global function ext3_panic Please comment ib whether this patch is correct or conflicts with pending changes. diffstat output: fs/ext3/balloc.c | 2 fs/ext3/dir.c | 2 fs/ext3/inode.c | 4 fs/ext3/resize.c | 4

On Saturday I finally upgraded a machine from CentOS 4.3 (I think) to 4.5 via yum. Seemed to went fine. However, during the following night /home got mounted read-only because of an EXT3-fs error. The next night happened the same. Also, today, I saw the first-ever kernel crash on this machine. The machine is about three years old or so, went into production two years ago with CentOS 4.1 or so and