Cores sent in another message to Nathan...
Furthermore, an hour or so later, they got the following Oops on the same box.
They called me an hour after that. I have since rebooted.
All filesystems are NFS exported sync,nowdelay.
Sep 13 01:14:14 nas2 kernel: Unable to handle kernel NULL pointer dereference
at virtual address 00000008
Sep 13 01:14:14 nas2 kernel: 801e9395
Sep 13 01:14:14 nas2 kernel: Oops: 0000
Sep 13 01:14:14 nas2 kernel: CPU: 0
Sep 13 01:14:14 nas2 kernel: EIP: 0010:[xfs_syncsub+2261/2976]
Sep 13 01:14:14 nas2 kernel: EIP: 0010:[<801e9395>]
Using defaults from ksymoops -t elf32-i386 -a i386
Sep 13 01:14:14 nas2 kernel: EFLAGS: 00010246
Sep 13 01:14:14 nas2 kernel: eax: bce0bbc0 ebx: a0ccc514 ecx: 00000000
edx: 00000000
Sep 13 01:14:14 nas2 kernel: esi: 00000000 edi: bce0bbc0 ebp: a0ccc514
esp: bfff5f00
Sep 13 01:14:14 nas2 kernel: ds: 0018 es: 0018 ss: 0018
Sep 13 01:14:14 nas2 kernel: Process kupdated (pid: 6, stackpage=bfff5000)
Sep 13 01:14:14 nas2 kernel: Stack: a0ccc514 00000000 00000000 00000001
00000008 00000008 00000040 00000000
Sep 13 01:14:14 nas2 kernel: 00000000 00000000 00000001 bcd144a0
8252e108 00000246 803109e0 8252e000
Sep 13 01:14:14 nas2 kernel: 82585200 80239036 82585200 00000000
8034c800 80316360 80316000 bfff4000
Sep 13 01:14:14 nas2 kernel: Call Trace: [AAC_QueueCommand+22/48]
[xfs_sync+21/32] [linvfs_write_super+39/48] [sync_supers+141/208]
[schedule_timeout+139/176]
Sep 13 01:14:14 nas2 kernel: Call Trace: [<80239036>] [<801e8ab5>]
[<801f9197>][<801373ad>] [<8011178b>]
Sep 13 01:14:14 nas2 kernel: [<8013625a>] [<ffff0018>] [<ffff0018>] [<8013659
8>] [<80105000>] [<801055a6>]
Sep 13 01:14:14 nas2 kernel: [<80136480>]
Sep 13 01:14:14 nas2 kernel: Code: 39 56 08 0f 85 42 f8 ff ff 8b 44 24 74 05
1401 00 00 50 e8
>>EIP; 801e9395 <pagebuf_unlock+543f5/64f00> <=====
Trace; 80239036 <scsi_free+1746/12570>
Trace; 801e8ab5 <pagebuf_unlock+53b15/64f00>
Trace; 801f9197 <pagebuf_unlock+641f7/64f00>
Trace; 801373ad <__wait_on_super+11d/160>
Trace; 8011178b <schedule_timeout+8b/140>
Trace; 8013625a <block_symlink+7fa/850>
Trace; ffff0018 <END_OF_CODE+3f656179/????>
Trace; ffff0018 <END_OF_CODE+3f656179/????>
Trace; 80136598 <block_sync_page+2e8/380>
Trace; 80105000 <gdt+4d94/4f04>
Trace; 801055a6 <kernel_thread+26/1a0>
Trace; 80136480 <block_sync_page+1d0/380>
Code; 801e9395 <pagebuf_unlock+543f5/64f00>
00000000 <_EIP>:
Code; 801e9395 <pagebuf_unlock+543f5/64f00> <=====
0: 39 56 08 cmp %edx,0x8(%esi) <=====
Code; 801e9398 <pagebuf_unlock+543f8/64f00>
3: 0f 85 42 f8 ff ff jne fffff84b <_EIP+0xfffff84b> 801e8be0 <pa
gebuf_unlock+53c40/64f00>
Code; 801e939e <pagebuf_unlock+543fe/64f00>
9: 8b 44 24 74 mov 0x74(%esp,1),%eax
Code; 801e93a2 <pagebuf_unlock+54402/64f00>
d: 05 14 01 00 00 add $0x114,%eax
Code; 801e93a7 <pagebuf_unlock+54407/64f00>
12: 50 push %eax
Code; 801e93a8 <pagebuf_unlock+54408/64f00>
13: e8 00 00 00 00 call 18 <_EIP+0x18> 801e93ad <pagebuf_unlock
+5440d/64f00>
1 warning and 1 error issued. Results may not be reliable.
-----Original Message-----
From: Nathan Scott [mailto:nathans@xxxxxxx]
Sent: Thursday, September 13, 2001 4:38
To: Christian, Chip
Cc: Linux XFS (E-mail)
Subject: Re: xfs_repair problems
hi,
On Thu, Sep 13, 2001 at 12:56:38AM -0400, Christian, Chip wrote:
> All,
>
> xfs_repair: phase4.c:1022: delete_orphanage: Assertion `(res == 0 && dirty ==
> 0)
> || (res == 1 && dirty == 1)' failed.
> Aborted (core dumped)
>
Its not immediately obvious what the problem is - any chance
you can send me me the core file and your xfs_repair binary?
(or put them somewhere I can download them?) That'll provide
some more clues.
thanks.
--
Nathan
|