Hi developers, please to meet you and congratats you for your great work. Let's go in my question. I have one box Intel(R) Xeon(TM) 1 CPU 3.06GHz (HT), 2gb ram and one SCSI storage controller QLogic Corp. QLA2200 64-bit Fibre Channel Adapter running debian stable (2.4.27 SMP) more Debian HBA Patch actuating like one Network Area Storage (NAS). This server shares theerteen volumes for more of the ninety clients via nfs with the XFS like filesystem. Well in the last days I needed to reboot this box because nfs server is stoping to work and I got the follow messages in '/var/log/messages'.
------------------------------------------- May 10 04:30:29 linpro367nas kernel: printing eip: May 10 04:30:29 linpro367nas kernel: c023bd2a May 10 04:30:29 linpro367nas kernel: Oops: 0000 May 10 04:30:29 linpro367nas kernel: CPU: 0 May 10 04:30:29 linpro367nas kernel: EIP: 0010:[linvfs_dentry_to_fh+42/160] Not tainted May 10 04:30:29 linpro367nas kernel: EFLAGS: 00010202 May 10 04:30:29 linpro367nas kernel: eax: 00000000 ebx: 0000000d ecx: dc315ba0 edx: dc315 b80 May 10 04:30:29 linpro367nas kernel: esi: f6221d30 edi: f6221cf0 ebp: f6221cb8 esp: f6221 cb8 May 10 04:30:29 linpro367nas kernel: ds: 0018 es: 0018 ss: 0018 May 10 04:30:29 linpro367nas kernel: Process nfsd (pid: 389, stackpage=f6221000) May 10 04:30:29 linpro367nas kernel: Stack: c9042da0 f6221cf0 00000000 c0148a21 f6221d20 ea0727 60 f6221d30 c03b9f00 May 10 04:30:29 linpro367nas kernel: c01a70cc ea072760 f6221d30 f6221cf0 00000001 dc315b a0 0000000d f5ee0b40 May 10 04:30:29 linpro367nas kernel: ea072760 f616c204 f34b7232 c01b1bd5 f6221d20 f5e278 00 ea072760 f616c204 May 10 04:30:29 linpro367nas kernel: Call Trace: [lookup_hash+65/224] [fh_compose+380/848] [ encode_entry+341/608] [nfs3svc_encode_entry_plus+37/48] [linvfs_readdir+373/528] May 10 04:30:29 linpro367nas kernel: [vfs_readdir+147/224] [nfs3svc_encode_entry_plus+0/48] [ nfsd_readdir+184/400] [nfs3svc_encode_entry_plus+0/48] [nfsd3_proc_readdirplus+184/320] [nfs3sv c_encode_entry_plus+0/48] May 10 04:30:29 linpro367nas kernel: [nfsd_dispatch+169/432] [svc_process+872/1441] [nfsd+510 /880] [arch_kernel_thread+35/48] [nfsd+0/880] May 10 04:30:29 linpro367nas kernel: May 10 04:30:29 linpro367nas kernel: Code: 8b 40 08 55 8b 4a 14 51 ff 50 50 8b 44 24 10 83 fb 0 3 89 06 May 17 09:17:11 linpro367nas kernel: kernel BUG at inode.c:1238! May 17 09:17:11 linpro367nas kernel: invalid operand: 0000 May 17 09:17:11 linpro367nas kernel: CPU: 1 May 17 09:17:11 linpro367nas kernel: EIP: 0010:[iput+258/784] Not tainted May 17 09:17:11 linpro367nas kernel: EFLAGS: 00010202 May 17 09:17:11 linpro367nas kernel: eax: cf006700 ebx: cf006660 ecx: 00000001 edx: 00000 003 May 17 09:17:11 linpro367nas kernel: esi: 00000000 edi: c03b9f00 ebp: f5ede000 esp: f5edf ef8 May 17 09:17:11 linpro367nas kernel: ds: 0018 es: 0018 ss: 0018 May 17 09:17:11 linpro367nas kernel: Process nfsd (pid: 366, stackpage=f5edf000) May 17 09:17:11 linpro367nas kernel: Stack: 00000000 e4f971e0 e4f97270 c0149ec9 cf006660 e4f971 e0 dfe57260 f6187c04 May 17 09:17:11 linpro367nas kernel: edb6dd40 c01a9f3e e4f971e0 edb6dd40 e4f971e0 f61b00 00 0000000a f6187c94 May 17 09:17:11 linpro367nas kernel: f6187c04 c01aeae7 f6187e00 f6187c04 ffffc000 e2cce0 a8 0000000a f6187e00 May 17 09:17:11 linpro367nas kernel: Call Trace: [vfs_unlink+329/560] [nfsd_unlink+254/496] [nfsd3_proc_remove+103/208] [nfsd_dispatch+169/432] [svc_process+872/1441] May 17 09:17:11 linpro367nas kernel: [nfsd+510/880] [arch_kernel_thread+35/48] [nfsd+0/880] May 17 09:17:11 linpro367nas kernel: May 17 09:17:11 linpro367nas kernel: Code: 0f 0b d6 04 d8 08 36 c0 89 5c 24 10 5b 5e 5f e9 0a e 6 ff ff ------------------------------------------- What can I do to fix this problem? Tks. -- Renan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
