Displaying 8 results from an estimated 8 matches for "htree_dirblock_to_tree".
2007 Aug 02
1
"htree_dirblock_to_tree: bad entry in directory" error
...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): 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.cri...
2012 May 06
1
Ext3 and drbd read-only remount problem.
...ith smartctl
-t long, they are ok. There are no messages with 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 s...
2008 Feb 25
2
ext3 errors
...initially but I think that is fixed now and I
can't see any hardware errors being logged (the system/log files are 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...
2007 Dec 10
2
unstable kernel after update to CentOS 4.5
...disk.
I didn't file it as a bug yet. I want to first 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...
2012 May 14
0
Weird problem with rsync 3.0.9
...bfa3e>] ? sync_buffer+0x0/0x40
[902361.152454] [<ffffffff812f74cb>] ? out_of_line_wait_on_bit+0x6b/0x77
[902361.152460] [<ffffffff810444d8>] ? wake_bit_function+0x0/0x23
[902361.152464] [<ffffffff810f6177>] ? ext3_bread+0x4c/0x6d
[902361.152468] [<ffffffff810faa22>] ? htree_dirblock_to_tree+0x33/0x13e
[902361.152472] [<ffffffff810b0655>] ? dput+0x23/0x13d
[902361.152475] [<ffffffff810faba9>] ? ext3_htree_fill_tree+0x7c/0x1e7
[902361.152479] [<ffffffff8109d927>] ? __kmalloc+0xf2/0x102
[902361.152483] [<ffffffff810f20d1>] ? ext3_readdir+0x173/0x554
[902361.15...
2009 Mar 24
1
Ext3 - Frequent read-only FS issues
...2.6.18-92.1.10.el5 #1 SMP x86_64
Dell PERC 6/i - Write back cache enabled
Battery available
2 * ST3500630AS 500GB in RAID1
Instances of EXT3 errors which caused read only FS :
a. ?EXT3-fs error (device sda3): ext3_lookup: unlinked inode 89065027 in dir
#89065024?
b. ?EST3-fs error (device sda3): htree_dirblock_to_tree: bad entry #65077525:
rec_len is smaller than minimal - offset=0, inode=0, rc_len=0, name_len=0?
c. ?EXT3-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory
#65077525: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
name_len=0 ?
d. ?kernel: EXT3-fs error (device...
2008 Mar 31
1
my centos switched alone its root fs to read-only
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
2016 Apr 13
3
Bug#820862: xen-hypervisor-4.4-amd64: Xen VM on Jessie freezes often with INFO: task jbd2/xvda2-8:111 blocked for more than 120 seconds
...wait_on_bit+0x77/0x90
[ 1080.060233] [<ffffffff810a7e90>] ? autoremove_wake_function+0x30/0x30
[ 1080.060246] [<ffffffffa007160b>] ? ext4_bread+0x5b/0x90 [ext4]
[ 1080.060253] [<ffffffffa007931a>] ? __ext4_read_dirblock+0x3a/0x3c0 [ext4]
[ 1080.060262] [<ffffffffa0079b80>] ? htree_dirblock_to_tree+0x40/0x190 [ext4]
[ 1080.060269] [<ffffffffa007aed1>] ? ext4_htree_fill_tree+0xc1/0x250 [ext4]
[ 1080.060274] [<ffffffff811b7b78>] ? path_openat+0x158/0x680
[ 1080.060279] [<ffffffff8117abb5>] ? free_pages_and_swap_cache+0x95/0xb0
[ 1080.060285] [<ffffffffa0069efb>] ? ext4_r...