W dniu 2010-06-08 09:54, Tsuyoshi Nagata pisze:
Hi (2010/06/08 5:12), Steve Brooks wrote:
Jun 7 19:45:21 sraid3 kernel: [<ffffffff800ec2a2>] inode_wait+0x0/0xd Jun 7 19:45:21 sraid3 kernel: [<ffffffff80063ab0>] out_of_line_wait_on_bit+0x6c/0x78 Jun 7 19:45:21 sraid3 kernel: [<ffffffff800a0aec>] wake_bit_function+0x0/0x23 Jun 7 19:45:21 sraid3 kernel: [<ffffffff8003dbbf>] ifind_fast+0x6e/0x83
This message was created at Linux/fs/inode.c:ifind_fast() The source code was bellows,
Linux/fs/inode.c: 912 static struct inode *ifind_fast(struct super_block *sb, 913 struct hlist_head *head, unsigned long ino) 914 { 915 struct inode *inode; 916 917 *LOCK* spin_lock(&inode_lock);<= This takes 918 inode = find_inode_fast(sb, head, ino);<= more 120s. 919 if (inode) { 920 __iget(inode); 921 *UNLOCK* spin_unlock(&inode_lock); 922 wait_on_inode(inode); 923 return inode; 924 } 925 spin_unlock(&inode_lock); 926 return NULL; 927 } 928
I guess your your file system has a trouble with i-node(file number) resources. CAUSES: Hard Disk trouble (bit error/raid trouble.) i-node trouble (overflow. etc.) Memory/CPU trouble(&inode_lock)
Buy Fresh Hard disks& rebuild them is convenience way. Or memtest86 can finds DIMM trouble.(or CPU, mother board) Or ext4 bug in 194.3.1 kernel, back to ext3!
Ok, then i will test all of my centos 5.5 32 nodes: cpu, ram, disks etc. This came with the kernel of Centos 5.5. Before there was'nt such errors/warrning. Redhat bugizilla: https://bugzilla.redhat.com/show_bug.cgi?id=573106
I.Piasecki
-tsuyoshi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos