Given the following Oopses, is it wise to continue running the XFS
filesystem, or might there be some other underlying problem that is causing
these Oopses?
Kernel 2.4.5 + XFS 1.0.1:
Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at virtual address 0cb73058
Nov 25 07:28:23 awacs kernel: printing eip:
Nov 25 07:28:23 awacs kernel: c01d6493
Nov 25 07:28:23 awacs kernel: *pde = 00000000
Nov 25 07:28:23 awacs kernel: Oops: 0000
Nov 25 07:28:23 awacs kernel: CPU: 0
Nov 25 07:28:23 awacs kernel: EIP: 0010:[xfs_inactive_free_eofblocks+615/720]
Nov 25 07:28:23 awacs kernel: EFLAGS: 00010206
Nov 25 07:28:23 awacs kernel: eax: 0cb73000 ebx: dfecf400 ecx: dfecf400 edx: ce19b830
Nov 25 07:28:23 awacs kernel: esi: c0042bd8 edi: da742f20 ebp: 00000000 esp: dffe7f2c
Nov 25 07:28:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
Nov 25 07:28:23 awacs kernel: Process kupdated (pid: 6, stackpage=dffe7000)
Nov 25 07:28:23 awacs kernel: Stack: dfec6c00 00000000 dfec6c44 dffe6650 00000001 dfecf514 00000010 00000001
Nov 25 07:28:23 awacs kernel: dfecf514 00000000 00000010 00000001 00000000 00000008 00000008 00000040
Nov 25 07:28:23 awacs kernel: 00000000 00000000 00000000 de64d500 df196f20 00000026 dfaeaa00 00000000
Nov 25 07:28:23 awacs kernel: Call Trace: [xfs_inactive_free_eofblocks+17/720] [load_msg+176/240] [block_write+1347/1376] [do_remount+122/172] [do_mount+537/740] [kernel_thread+35/48]
Nov 25 07:28:23 awacs kernel:
Nov 25 07:28:23 awacs kernel: Code: f7 40 58 ff 01 00 00 75 14 66 83 be 52 01 00 00 00 75 0a 8b
Kernel 2.4.14 + XFS 1.0.2:
Nov 26 04:16:23 awacs kernel: Unable to handle kernel paging request at virtual address ff689108
Nov 26 04:16:23 awacs kernel: printing eip:
Nov 26 04:16:23 awacs kernel: c01c5955
Nov 26 04:16:23 awacs kernel: *pde = 00000000
Nov 26 04:16:23 awacs kernel: Oops: 0000
Nov 26 04:16:23 awacs kernel: CPU: 1
Nov 26 04:16:23 awacs kernel: EIP: 0010:[xfs_syncsub+2309/3056] Not tainted
Nov 26 04:16:23 awacs kernel: EFLAGS: 00010246
Nov 26 04:16:23 awacs kernel: eax: 00000000 ebx: 00000000 ecx: dffbe914 edx: c490bbd8
Nov 26 04:16:23 awacs kernel: esi: ff689100 edi: c84ab740 ebp: c03c4760 esp: c1955f24
Nov 26 04:16:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
Nov 26 04:16:23 awacs kernel: Process kupdated (pid: 7, stackpage=c1955000)
Nov 26 04:16:23 awacs kernel: Stack: dffbe914 00000001 00000001 00000000 00000001 00000008 00000008 00000040
Nov 26 04:16:23 awacs kernel: 00000000 00000000 00000000 dd2bda00 c79a91a0 c197bfac c0114539 c1955f9c
Nov 26 04:16:23 awacs kernel: de302f40 dbde0000 0000001a 00000046 00000286 00000001 00000286 00000003
Nov 26 04:16:23 awacs kernel: Call Trace: [schedule+969/1504] [xfs_sync+21/32] [linvfs_write_super+42/48] [sync_supers+199/256] [sync_old_buffers+44/128]
Nov 26 04:16:23 awacs kernel: [kupdate+317/336] [_stext+0/64] [kernel_thread+38/48] [kupdate+0/336]
Nov 26 04:16:23 awacs kernel:
Nov 26 04:16:23 awacs kernel: Code: 39 56 08 0f 85 22 f8 ff ff 8b 44 24 78 05 14 01 00 00 50 e8
Just as a data point I've been running XFS with 2.4.14 on three machines
since Saturday (two machines on 24/7) + my laptop ,quite a lot of disk
access on my laptop (Debian upgrade and install) and its been fine.
> -----Original Message-----
> From: Pascal Haakmat [mailto:[email protected]]
> Sent: 28 November 2001 14:57
> To: [email protected]
> Subject: XFS Oopses with 2.4.5 and 2.4.14?
>
>
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem
> that is causing
> these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging
> request at virtual address 0cb73058
> Nov 25 07:28:23 awacs kernel: printing eip:
> Nov 25 07:28:23 awacs kernel: c01d6493
> Nov 25 07:28:23 awacs kernel: *pde = 00000000
> Nov 25 07:28:23 awacs kernel: Oops: 0000
> Nov 25 07:28:23 awacs kernel: CPU: 0
> Nov 25 07:28:23 awacs kernel: EIP:
> 0010:[xfs_inactive_free_eofblocks+615/720]
> Nov 25 07:28:23 awacs kernel: EFLAGS: 00010206
> Nov 25 07:28:23 awacs kernel: eax: 0cb73000 ebx: dfecf400
> ecx: dfecf400 edx: ce19b830
> Nov 25 07:28:23 awacs kernel: esi: c0042bd8 edi: da742f20
> ebp: 00000000 esp: dffe7f2c
> Nov 25 07:28:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 25 07:28:23 awacs kernel: Process kupdated (pid: 6,
> stackpage=dffe7000)
> Nov 25 07:28:23 awacs kernel: Stack: dfec6c00 00000000
> dfec6c44 dffe6650 00000001 dfecf514 00000010 00000001
> Nov 25 07:28:23 awacs kernel: dfecf514 00000000
> 00000010 00000001 00000000 00000008 00000008 00000040
> Nov 25 07:28:23 awacs kernel: 00000000 00000000
> 00000000 de64d500 df196f20 00000026 dfaeaa00 00000000
> Nov 25 07:28:23 awacs kernel: Call Trace:
> [xfs_inactive_free_eofblocks+17/720] [load_msg+176/240]
> [block_write+1347/1376] [do_remount+122/172]
> [do_mount+537/740] [kernel_thread+35/48]
> Nov 25 07:28:23 awacs kernel:
> Nov 25 07:28:23 awacs kernel: Code: f7 40 58 ff 01 00 00 75
> 14 66 83 be 52 01 00 00 00 75 0a 8b
>
> Kernel 2.4.14 + XFS 1.0.2:
>
> Nov 26 04:16:23 awacs kernel: Unable to handle kernel paging
> request at virtual address ff689108
> Nov 26 04:16:23 awacs kernel: printing eip:
> Nov 26 04:16:23 awacs kernel: c01c5955
> Nov 26 04:16:23 awacs kernel: *pde = 00000000
> Nov 26 04:16:23 awacs kernel: Oops: 0000
> Nov 26 04:16:23 awacs kernel: CPU: 1
> Nov 26 04:16:23 awacs kernel: EIP:
> 0010:[xfs_syncsub+2309/3056] Not tainted
> Nov 26 04:16:23 awacs kernel: EFLAGS: 00010246
> Nov 26 04:16:23 awacs kernel: eax: 00000000 ebx: 00000000
> ecx: dffbe914 edx: c490bbd8
> Nov 26 04:16:23 awacs kernel: esi: ff689100 edi: c84ab740
> ebp: c03c4760 esp: c1955f24
> Nov 26 04:16:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 26 04:16:23 awacs kernel: Process kupdated (pid: 7,
> stackpage=c1955000)
> Nov 26 04:16:23 awacs kernel: Stack: dffbe914 00000001
> 00000001 00000000 00000001 00000008 00000008 00000040
> Nov 26 04:16:23 awacs kernel: 00000000 00000000
> 00000000 dd2bda00 c79a91a0 c197bfac c0114539 c1955f9c
> Nov 26 04:16:23 awacs kernel: de302f40 dbde0000
> 0000001a 00000046 00000286 00000001 00000286 00000003
> Nov 26 04:16:23 awacs kernel: Call Trace: [schedule+969/1504]
> [xfs_sync+21/32] [linvfs_write_super+42/48]
> [sync_supers+199/256] [sync_old_buffers+44/128]
> Nov 26 04:16:23 awacs kernel: [kupdate+317/336]
> [_stext+0/64] [kernel_thread+38/48] [kupdate+0/336]
> Nov 26 04:16:23 awacs kernel:
> Nov 26 04:16:23 awacs kernel: Code: 39 56 08 0f 85 22 f8 ff
> ff 8b 44 24 78 05 14 01 00 00 50 e8
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Am Mittwoch, 28. November 2001 15:57 schrieb Pascal Haakmat:
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem that is
> causing these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at
[...]
I had these problems in the past with a inconsitent XFS Filesystem, I'd
recommend to run xfs_repair on your XFS filesystems, using a external
Rescue CD - bootdisk/bootCD. If you have none handy, drop me a mail.
The fs-troubles on my server was arising using a Highend-Caching
controller (ICP-Vortex), and not flushing the cache before power down.
After several power downs the XFS had headaches, and I had such
kernel-oops.
mfG
Jojo
--
J?rgen Sauer - AutomatiX GmbH, +49-4209-4699, [email protected] **
** Das Linux Systemhaus - Service - Support - Server - L?sungen **
http://www.automatix.de to Mail me: remove: -not-for-spawm- **
Hi Pascal -
Did you compile these kernels yourself, and if so, what compiler did you
use?
Can you reproduce this reliably?
I'd be happy to help with debugging this if you'd like, you might also
take this over to [email protected].
-Eric
In article <[email protected]>, "Pascal Haakmat"
<[email protected]> wrote:
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem that is
> causing these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at
> virtual address 0cb73058 Nov 25 07:28:23 awacs kernel: printing eip:
> Nov 25 07:28:23 awacs kernel: c01d6493 Nov 25 07:28:23 awacs kernel:
> *pde = 00000000 Nov 25 07:28:23 awacs kernel: Oops: 0000 Nov 25 07:28:23
> awacs kernel: CPU: 0 Nov 25 07:28:23 awacs kernel: EIP:
> 0010:[xfs_inactive_free_eofblocks+615/720] Nov 25 07:28:23 awacs kernel:
> EFLAGS: 00010206 Nov 25 07:28:23 awacs kernel: eax: 0cb73000 ebx:
> dfecf400 ecx: dfecf400 edx: ce19b830 Nov 25 07:28:23 awacs kernel:
> esi: c0042bd8 edi: da742f20 ebp: 00000000 esp: dffe7f2c Nov 25
> 07:28:23 awacs kernel: ds: 0018 es: 0018 ss: 0018 Nov 25 07:28:23
> awacs kernel: Process kupdated (pid: 6, stackpage=dffe7000) Nov 25
> 07:28:23 awacs kernel: Stack: dfec6c00 00000000 dfec6c44 dffe6650
> 00000001 dfecf514 00000010 00000001 Nov 25 07:28:23 awacs kernel:
> dfecf514 00000000 00000010 00000001 00000000 00000008 00000008 00000040
> Nov 25 07:28:23 awacs kernel: 00000000 00000000 00000000 de64d500
> df196f20 00000026 dfaeaa00 00000000 Nov 25 07:28:23 awacs kernel: Call
> Trace: [xfs_inactive_free_eofblocks+17/720] [load_msg+176/240]
> [block_write+1347/1376] [do_remount+122/172] [do_mount+537/740]
> [kernel_thread+35/48] Nov 25 07:28:23 awacs kernel:
> Nov 25 07:28:23 awacs kernel: Code: f7 40 58 ff 01 00 00 75 14 66 83 be
> 52 01 00 00 00 75 0a 8b
>
> Kernel 2.4.14 + XFS 1.0.2:
>
> Nov 26 04:16:23 awacs kernel: Unable to handle kernel paging request at
> virtual address ff689108 Nov 26 04:16:23 awacs kernel: printing eip:
> Nov 26 04:16:23 awacs kernel: c01c5955 Nov 26 04:16:23 awacs kernel:
> *pde = 00000000 Nov 26 04:16:23 awacs kernel: Oops: 0000 Nov 26 04:16:23
> awacs kernel: CPU: 1 Nov 26 04:16:23 awacs kernel: EIP:
> 0010:[xfs_syncsub+2309/3056] Not tainted Nov 26 04:16:23 awacs
> kernel: EFLAGS: 00010246 Nov 26 04:16:23 awacs kernel: eax: 00000000
> ebx: 00000000 ecx: dffbe914 edx: c490bbd8 Nov 26 04:16:23 awacs
> kernel: esi: ff689100 edi: c84ab740 ebp: c03c4760 esp: c1955f24 Nov
> 26 04:16:23 awacs kernel: ds: 0018 es: 0018 ss: 0018 Nov 26 04:16:23
> awacs kernel: Process kupdated (pid: 7, stackpage=c1955000) Nov 26
> 04:16:23 awacs kernel: Stack: dffbe914 00000001 00000001 00000000
> 00000001 00000008 00000008 00000040 Nov 26 04:16:23 awacs kernel:
> 00000000 00000000 00000000 dd2bda00 c79a91a0 c197bfac c0114539 c1955f9c
> Nov 26 04:16:23 awacs kernel: de302f40 dbde0000 0000001a 00000046
> 00000286 00000001 00000286 00000003 Nov 26 04:16:23 awacs kernel: Call
> Trace: [schedule+969/1504] [xfs_sync+21/32] [linvfs_write_super+42/48]
> [sync_supers+199/256] [sync_old_buffers+44/128] Nov 26 04:16:23 awacs
> kernel: [kupdate+317/336] [_stext+0/64] [kernel_thread+38/48]
> [kupdate+0/336] Nov 26 04:16:23 awacs kernel:
> Nov 26 04:16:23 awacs kernel: Code: 39 56 08 0f 85 22 f8 ff ff 8b 44 24
> 78 05 14 01 00 00 50 e8 -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to [email protected] More majordomo
> info at http://vger.kernel.org/majordomo-info.html Please read the FAQ
> at http://www.tux.org/lkml/
Pascal Haakmat schrieb:
>
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem that is causing
> these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
I crosspost this to xfs-mailing list.
The filesystem itself looks good.
I'm still experiencing problems in the nfsd codepath. 2.4.4-xfs fixed a bug for this.
Now I run 2.4.9-xfs and wait for the next crash that seems to happen when
uptime gets > 13 days ;-(
BTW, it is recommended to compile the kernel with
$ kgcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at virtual address 0cb73058
> Nov 25 07:28:23 awacs kernel: printing eip:
> Nov 25 07:28:23 awacs kernel: c01d6493
> Nov 25 07:28:23 awacs kernel: *pde = 00000000
> Nov 25 07:28:23 awacs kernel: Oops: 0000
> Nov 25 07:28:23 awacs kernel: CPU: 0
> Nov 25 07:28:23 awacs kernel: EIP: 0010:[xfs_inactive_free_eofblocks+615/720]
> Nov 25 07:28:23 awacs kernel: EFLAGS: 00010206
> Nov 25 07:28:23 awacs kernel: eax: 0cb73000 ebx: dfecf400 ecx: dfecf400 edx: ce19b830
> Nov 25 07:28:23 awacs kernel: esi: c0042bd8 edi: da742f20 ebp: 00000000 esp: dffe7f2c
> Nov 25 07:28:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 25 07:28:23 awacs kernel: Process kupdated (pid: 6, stackpage=dffe7000)
> Nov 25 07:28:23 awacs kernel: Stack: dfec6c00 00000000 dfec6c44 dffe6650 00000001 dfecf514 00000010 00000001
> Nov 25 07:28:23 awacs kernel: dfecf514 00000000 00000010 00000001 00000000 00000008 00000008 00000040
> Nov 25 07:28:23 awacs kernel: 00000000 00000000 00000000 de64d500 df196f20 00000026 dfaeaa00 00000000
> Nov 25 07:28:23 awacs kernel: Call Trace: [xfs_inactive_free_eofblocks+17/720] [load_msg+176/240] [block_write+1347/1376] [do_remount+122/172] [do_mount+537/740] [kernel_thread+35/48]
> Nov 25 07:28:23 awacs kernel:
> Nov 25 07:28:23 awacs kernel: Code: f7 40 58 ff 01 00 00 75 14 66 83 be 52 01 00 00 00 75 0a 8b
>
> Kernel 2.4.14 + XFS 1.0.2:
>
> Nov 26 04:16:23 awacs kernel: Unable to handle kernel paging request at virtual address ff689108
> Nov 26 04:16:23 awacs kernel: printing eip:
> Nov 26 04:16:23 awacs kernel: c01c5955
> Nov 26 04:16:23 awacs kernel: *pde = 00000000
> Nov 26 04:16:23 awacs kernel: Oops: 0000
> Nov 26 04:16:23 awacs kernel: CPU: 1
> Nov 26 04:16:23 awacs kernel: EIP: 0010:[xfs_syncsub+2309/3056] Not tainted
> Nov 26 04:16:23 awacs kernel: EFLAGS: 00010246
> Nov 26 04:16:23 awacs kernel: eax: 00000000 ebx: 00000000 ecx: dffbe914 edx: c490bbd8
> Nov 26 04:16:23 awacs kernel: esi: ff689100 edi: c84ab740 ebp: c03c4760 esp: c1955f24
> Nov 26 04:16:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 26 04:16:23 awacs kernel: Process kupdated (pid: 7, stackpage=c1955000)
> Nov 26 04:16:23 awacs kernel: Stack: dffbe914 00000001 00000001 00000000 00000001 00000008 00000008 00000040
> Nov 26 04:16:23 awacs kernel: 00000000 00000000 00000000 dd2bda00 c79a91a0 c197bfac c0114539 c1955f9c
> Nov 26 04:16:23 awacs kernel: de302f40 dbde0000 0000001a 00000046 00000286 00000001 00000286 00000003
> Nov 26 04:16:23 awacs kernel: Call Trace: [schedule+969/1504] [xfs_sync+21/32] [linvfs_write_super+42/48] [sync_supers+199/256] [sync_old_buffers+44/128]
> Nov 26 04:16:23 awacs kernel: [kupdate+317/336] [_stext+0/64] [kernel_thread+38/48] [kupdate+0/336]
> Nov 26 04:16:23 awacs kernel:
> Nov 26 04:16:23 awacs kernel: Code: 39 56 08 0f 85 22 f8 ff ff 8b 44 24 78 05 14 01 00 00 50 e8
> -
28/11/01 09:48, Eric Sandeen wrote:
> Hi Pascal -
>
> Did you compile these kernels yourself, and if so, what compiler did you
> use?
Yes:
Linux version 2.4.5-xfs-1.0.1 ([email protected]) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #10 SMP Fri Sep 21 18:34:40 CEST 2001
Linux version 2.4.14-xfs-1.0.2 ([email protected]) (gcc version 2.96
20000731 (Red Hat Linux 7.1 2.96-98)) #2 SMP Sun Nov 25 08:15:50 CET 2001
> Can you reproduce this reliably?
No, that is to say, I haven't tried.
Somebody else has suggested FS corruption as the cause of these Oopses. That
might very well be the case. On multiple occassions (perhaps coinciding with
the Oopses, sorry I can't be more specific), my system has hung when trying
to write to a file, and I would be left with files looking somewhat like
this (from memory):
$ ls -lhsa spook.wav
0 -rw-r--r-- 1 p p 165k Nov 25 09:04 spook.wav
Up until now I just rm'd these files and continued, but I suppose I can try
an xfs_repair from the boot CD.
> I'd be happy to help with debugging this if you'd like, you might also
> take this over to [email protected].
Thanks.