search for: rec_len

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 - offset=0, inode=861103477, rec_len=95, name_len=95 Apr 12 04:08:17 hal kernel: EXT3-fs error (device md(9,...

...ut if it rejoins, it will not get the SID entry it >> had before? >> > > > Samba-tool domain demote --remove-other-dead-server=DEAD_SERVER > > Rowland > tdb> open /var/lib/samba/private/secrets.tdb tdb> list hash=31 rec: hash=31 offset=0x0000ccc8 next=0x00000000 rec_len=116 key_len=20 data_len=68 full_hash=0x6344070e magic=0x26011999 hash=40 rec: hash=40 offset=0x0000cc48 next=0x00000000 rec_len=104 key_len=12 data_len=68 full_hash=0x2a4c7c2e magic=0x26011999 hash=81 rec: hash=81 offset=0x0000cb48 next=0x00000000 rec_len=48 key_len=28 data_len=5 full_hash=0x046...

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 these entries are in the logfile...

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 #50619: rec_len is too small for name_len - offset=0, inode=574907, rec_len=12, name_len=9 Jan 6 22:18:43 jaguar kernel: EXT3-...

...>>> had before? >>> >> >> >> Samba-tool domain demote --remove-other-dead-server=DEAD_SERVER >> >> Rowland >> > tdb> open /var/lib/samba/private/secrets.tdb > tdb> list > hash=31 > rec: hash=31 offset=0x0000ccc8 next=0x00000000 rec_len=116 key_len=20 > data_len=68 full_hash=0x6344070e magic=0x26011999 > hash=40 > rec: hash=40 offset=0x0000cc48 next=0x00000000 rec_len=104 key_len=12 > data_len=68 full_hash=0x2a4c7c2e magic=0x26011999 > hash=81 > rec: hash=81 offset=0x0000cb48 next=0x00000000 rec_len=48 key_len=...

...data mode. init_special_inode: bogus i_mode (113301) init_special_inode: bogus i_mode (170101) init_special_inode: bogus i_mode (115140) init_special_inode: bogus i_mode (117302) init_special_inode: bogus i_mode (111700) EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #143278260: rec_len % 4 != 0 - offset=0, inode=1857588108, rec_len=8466, name_len=34 Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (111501) Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (113301) Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (170101) Dec 2...

...: Allocating block in system zone - block = 20251151 Oct 19 16:04:39 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_new_block: Allocating block in system zone - block = 20251152 Oct 19 16:04:43 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_add_entry: bad entry in directory #10125314: rec_len %% 4 != 0 - offset=0, inode=4288315399, rec_len=65535, name_len=255 Oct 19 16:04:44 noname last message repeated 53 times Oct 19 16:05:04 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_add_entry: bad entry in directory #10125314: rec_len %% 4 != 0 - offset=0, inode=4288315399, rec_len=6553...

...ith disks problems in /var/log/messages | dmesg. I've made fsck tonight but 3 hours after it has finished the problem repeated once more (under heavy load). /var/log/messages: May 6 06:22:27 srv1a kernel: EXT3-fs error (device drbd0): htree_dirblock_to_tree: bad entry in directory #43024813: rec_len % 4 != 0 - offset=73728, inode=1701012818, rec_len=30313, name_len=101 May 6 06:22:27 srv1a kernel: Aborting journal on device drbd0. May 6 06:22:28 srv1a kernel: journal commit I/O error May 6 06:22:28 srv1a kernel: ext3_abort called. May 6 06:22:28 srv1a kernel: journal commit I/O error May...

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? > Samba-tool domain demote --remove-other-dead-server=DEAD_SERVER Rowland

...t;>> >>> >>> Samba-tool domain demote --remove-other-dead-server=DEAD_SERVER >>> >>> Rowland >>> >> tdb> open /var/lib/samba/private/secrets.tdb >> tdb> list >> hash=31 >> rec: hash=31 offset=0x0000ccc8 next=0x00000000 rec_len=116 key_len=20 >> data_len=68 full_hash=0x6344070e magic=0x26011999 >> hash=40 >> rec: hash=40 offset=0x0000cc48 next=0x00000000 rec_len=104 key_len=12 >> data_len=68 full_hash=0x2a4c7c2e magic=0x26011999 >> hash=81 >> rec: hash=81 offset=0x0000cb48 next=0x0000...

...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, name_len=109 May 21 14:07:23 glass kernel: EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109 May 21 14:07:23 glass kernel: EXT3-fs warning...

Just had this problem on linux 2.5.50. MikaL

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 - offset=0, inode=607908378, rec_len=18495, name_len=70 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884829: directory entry across blocks - offset=0, inode=2...

...e on different drives). About once a week, I get an error like this, and the partition switches to read-only. --- Feb 24 04:48:20 linbackup1 kernel: EXT3-fs error (device md3): htree_dirblock_to_tree: bad entry in directory #869973: directory entry across bloc ks - offset=0, inode=3915132787, rec_len=42464, name_len=11 Feb 24 04:48:20 linbackup1 kernel: Aborting journal on device md3. Feb 24 04:48:20 linbackup1 kernel: ext3_abort called. Feb 24 04:48:20 linbackup1 kernel: EXT3-fs error (device md3): ext3_journal_start_sb: Detected aborted journal Feb 24 04:48:20 linbackup1 kernel: Remounting f...

...gather some more information or get some help. Here are some details. Kernel was updated from 2.6.9-34.0.2.EL to 2.6.9-55.0.12.EL. There is not a single package update missing now. Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): htree_dirblock_to_tree: bad entry in directory #1330023: rec_len % 4 != 0 - offset=10264, inode=808542775, rec_len=13621, name_len=100 Dec 9 04:30:35 nx10 kernel: Aborting journal on device hda3. Dec 9 04:30:35 nx10 kernel: ext3_abort called. Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): ext3_journal_start_sb: Detected aborted journal Dec 9 04:30:...

...xt3 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): htree_dirblock_to_tree: bad entry in directory #3616894: rec_len is too small for name_len - offset=103576, inode=3619715, rec_len=12, name_len=132 2007-08-02 04:02:25 kern.err www kernel: Aborting journal on device md2. 2007-08-02 04:02:25 kern.crit www kernel: ext3_abort called. 2007-08-02 04:02:25 kern.crit www kernel: EXT3-fs error (device md2):...

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

...nad.swb.de). hdc: timeout waiting for DMA ide_dmaproc: chipset supported ide_dma_timeout func only: 14 hdc: status timeout: status=0xd0 { Busy } hdd: DMA disabled hdc: drive not ready for command ide1: reset: success EXT3-fs error (device ide1(22,65)): ext3_readdir: bad entry in directory #2665467: rec_len % 4 != 0 - offset=0, inode=762621470, rec_len=44574, name_len=110 Assertion failure in journal_bmap_Rbbdc8009() at journal.c:602: "ret != 0" ------------[ cut here ]------------ kernel BUG at journal.c:602! invalid operand: 0000 Kernel 2.4.9-31 CPU: 0 EIP: 0010:[<c8805368>]...

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 smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: attempt to access beyond end of devic...

...tem 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 #14370410: rec_len % 4 != 0 - offset=0, inode=1309281588, rec_len=16761, name_len=78 Aborting journal on device dm-4. ext3_abort called. EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-4) in start_transaction: Journal has aborted EX...