similar to: ext3 errors

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

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

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

Hi all, I have a bunch of mail servers running postfix (external smtp), qmail (LDA) and courier IMAP/POP. Frequently, Ext3 filesystem goes into read-only mode forcing recovery using fsck. Below are the errors we have seen so far on these systems and those systems config. The ext3 errors are common in many cases. 1. Red Hat Enterprise Linux Server release 5.2 (Tikanga) 2.6.18-92.1.10.el5

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 -

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

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

On 05/01/2023 12:19, Zombie Ryushu via samba wrote: > 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

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

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

My test server was in very eavy load, running kolab's components: postfix, cyrus-imap and openldap A second test machine was sending, and reading emails as fast as it can. The CPU was never idle ! I left the server at about 17H30 and at 22H I find it "uncommitted" (difficult to work when the partition in read-only !) However the mount command report it as RW ! The /boot is still RW

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,

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

I'm looking for some recommendations on where to go with a problem i'm running across. A filesystem under load put itself in readonly mode and the following can be found under dmesg.. any suggestions on root cause? hardware wise it's got a pair of PATA drives connected to a 3ware card in RAID10 configuration. EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory

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

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

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