FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > EXT3 Users

 
 
LinkBack Thread Tools
 
Old 02-25-2009, 03:13 PM
Jack Neely
 
Default ext3 kernel panic

Folks,

I have a RHEL 3 production Cyrus IMAP server that has kernel paniced
twice in as many weeks with something similar to the below. The /imap
partition (where the IO was in question) is about 98% full with about
6.2G free and is hosted on a fiber connected EMC Clariion lun.
Currently running kernel 2.4.21-15.0.4.ELsmp.

I know things are old here, and the machine is on the upgrade list, but
I need to do due diligence to figure out how serious this error is.
Does anyone have any advice why this is happening?

Thanks,
Jack Neely


Unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
f88d2863
*pde = 299d3001
*pte = 00000000
Oops: 0002
audit autofs openafs e1000 iptable_filter ip_tables floppy microcode emcphr emcpmpap emcpmpaa emcpmpc emcpmp sg emcp emcpsf loop lvm-mod keybdev mousedev hid
CPU: 0
EIP: 0060:[<f88d2863>] Tainted: P
EFLAGS: 00010213

EIP is at ext3_orphan_del [ext3] 0x73 (2.4.21-15.0.4.ELsmp/i686)
eax: c520d360 ebx: e3fc8900 ecx: e3fc8aac edx: 00000000
esi: 00000000 edi: c520d000 ebp: c520d360 esp: eed8fddc
ds: 0068 es: 0068 ss: 0068
Process imapd (pid: 7628, stackpage=eed8f000)
Stack: e4de9940 eed8e000 c69b6200 e9ffde00 f88b8445 000f8094 c520d0fc e1ee4e80
00000007 00000292 e3fc8900 00000000 eed8e000 f88cc72c c69b6200 e3fc8900
e4de9940 eed8e000 e9ffde00 f88cc84c e4de9940 e3fc8900 ee6d7500 e3fc8900
Call Trace: [<f88b8445>] journal_start_Rsmp_25661df5 [jbd] 0xa5 (0xeed8fdec)
[<f88cc72c>] start_transaction [ext3] 0x8c (0xeed8fe10)
[<f88cc84c>] ext3_delete_inode [ext3] 0x8c (0xeed8fe28)
[<f88cc7c0>] ext3_delete_inode [ext3] 0x0 (0xeed8fe3c)
[<c017ccd0>] iput [kernel] 0x150 (0xeed8fe44)
[<c0179afa>] dput [kernel] 0xca (0xeed8fe60)
[<c0161a5b>] __fput [kernel] 0xbb (0xeed8fe74)
[<c015fc0e>] filp_close [kernel] 0x8e (0xeed8fe90)
[<c012bf6c>] put_files_struct [kernel] 0x6c (0xeed8feac)
[<c012c85a>] do_exit [kernel] 0x1ba (0xeed8fec8)
[<c012cbbb>] do_group_exit [kernel] 0x8b (0xeed8fee4)
[<c013656b>] get_signal_to_deliver [kernel] 0x20b (0xeed8fef8)
[<c010bdd4>] do_signal [kernel] 0x64 (0xeed8ff20)
[<c0175a56>] sys_select [kernel] 0x296 (0xeed8ff60)

Code: 89 42 04 89 10 c7 41 04 00 00 00 00 89 8b ac 01 00 00 89 8b

Kernel panic: Fatal exception

--
Jack Neely <jjneely@ncsu.edu>
Linux Czar, OIT Campus Linux Services
Office of Information Technology, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-25-2009, 03:22 PM
Eric Sandeen
 
Default ext3 kernel panic

Jack Neely wrote:
> Folks,
>
> I have a RHEL 3 production Cyrus IMAP server that has kernel paniced
> twice in as many weeks with something similar to the below. The /imap
> partition (where the IO was in question) is about 98% full with about
> 6.2G free and is hosted on a fiber connected EMC Clariion lun.
> Currently running kernel 2.4.21-15.0.4.ELsmp.
>
> I know things are old here, and the machine is on the upgrade list, but
> I need to do due diligence to figure out how serious this error is.
> Does anyone have any advice why this is happening?
>
> Thanks,
> Jack Neely
>

That's not only an old distro, but an un-updated installation. I'd get
the latest RHEL3 kernel and peruse the changelog, for starters, to see
if it looks like this might have been fixed (although I don't see
anything offhand).

-Eric

> Unable to handle kernel NULL pointer dereference at virtual address 00000004
> printing eip:
> f88d2863
> *pde = 299d3001
> *pte = 00000000
> Oops: 0002
> audit autofs openafs e1000 iptable_filter ip_tables floppy microcode emcphr emcpmpap emcpmpaa emcpmpc emcpmp sg emcp emcpsf loop lvm-mod keybdev mousedev hid
> CPU: 0
> EIP: 0060:[<f88d2863>] Tainted: P
> EFLAGS: 00010213
>
> EIP is at ext3_orphan_del [ext3] 0x73 (2.4.21-15.0.4.ELsmp/i686)
> eax: c520d360 ebx: e3fc8900 ecx: e3fc8aac edx: 00000000
> esi: 00000000 edi: c520d000 ebp: c520d360 esp: eed8fddc
> ds: 0068 es: 0068 ss: 0068
> Process imapd (pid: 7628, stackpage=eed8f000)
> Stack: e4de9940 eed8e000 c69b6200 e9ffde00 f88b8445 000f8094 c520d0fc e1ee4e80
> 00000007 00000292 e3fc8900 00000000 eed8e000 f88cc72c c69b6200 e3fc8900
> e4de9940 eed8e000 e9ffde00 f88cc84c e4de9940 e3fc8900 ee6d7500 e3fc8900
> Call Trace: [<f88b8445>] journal_start_Rsmp_25661df5 [jbd] 0xa5 (0xeed8fdec)
> [<f88cc72c>] start_transaction [ext3] 0x8c (0xeed8fe10)
> [<f88cc84c>] ext3_delete_inode [ext3] 0x8c (0xeed8fe28)
> [<f88cc7c0>] ext3_delete_inode [ext3] 0x0 (0xeed8fe3c)
> [<c017ccd0>] iput [kernel] 0x150 (0xeed8fe44)
> [<c0179afa>] dput [kernel] 0xca (0xeed8fe60)
> [<c0161a5b>] __fput [kernel] 0xbb (0xeed8fe74)
> [<c015fc0e>] filp_close [kernel] 0x8e (0xeed8fe90)
> [<c012bf6c>] put_files_struct [kernel] 0x6c (0xeed8feac)
> [<c012c85a>] do_exit [kernel] 0x1ba (0xeed8fec8)
> [<c012cbbb>] do_group_exit [kernel] 0x8b (0xeed8fee4)
> [<c013656b>] get_signal_to_deliver [kernel] 0x20b (0xeed8fef8)
> [<c010bdd4>] do_signal [kernel] 0x64 (0xeed8ff20)
> [<c0175a56>] sys_select [kernel] 0x296 (0xeed8ff60)
>
> Code: 89 42 04 89 10 c7 41 04 00 00 00 00 89 8b ac 01 00 00 89 8b
>
> Kernel panic: Fatal exception
>

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-25-2009, 05:22 PM
Jack Neely
 
Default ext3 kernel panic

On Wed, Feb 25, 2009 at 10:22:46AM -0600, Eric Sandeen wrote:
> Jack Neely wrote:
> > Folks,
> >
> > I have a RHEL 3 production Cyrus IMAP server that has kernel paniced
> > twice in as many weeks with something similar to the below. The /imap
> > partition (where the IO was in question) is about 98% full with about
> > 6.2G free and is hosted on a fiber connected EMC Clariion lun.
> > Currently running kernel 2.4.21-15.0.4.ELsmp.
> >
> > I know things are old here, and the machine is on the upgrade list, but
> > I need to do due diligence to figure out how serious this error is.
> > Does anyone have any advice why this is happening?
> >
> > Thanks,
> > Jack Neely
> >
>
> That's not only an old distro, but an un-updated installation. I'd get
> the latest RHEL3 kernel and peruse the changelog, for starters, to see
> if it looks like this might have been fixed (although I don't see
> anything offhand).
>
> -Eric
>

I'm caught between a rock and a hard place due to the EMC PowerPath
binary only kernel crack. Which makes it painful to both me and my
customers to regularly upgrade the kernel. Not to mention the EMC
supportability matrix of doom.

I have 11 other imap servers configured identically that are not
regularly panicing. I'm trying to figure out what specifically could be
affecting this one machine or that isn't affecting the others. The only
change log entry that seems close is:

- fix O_SYNC EIO error propagation through ext3/jbd (Stephen
Tweedie)

from kernel-2.4.21-34.EL. Is that anywhere close?

Jack

--
Jack Neely <jjneely@ncsu.edu>
Linux Czar, OIT Campus Linux Services
Office of Information Technology, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-25-2009, 06:21 PM
Eric Sandeen
 
Default ext3 kernel panic

Jack Neely wrote:

> I'm caught between a rock and a hard place due to the EMC PowerPath
> binary only kernel crack. Which makes it painful to both me and my
> customers to regularly upgrade the kernel. Not to mention the EMC
> supportability matrix of doom.
>
> I have 11 other imap servers configured identically that are not
> regularly panicing. I'm trying to figure out what specifically could be
> affecting this one machine or that isn't affecting the others. The only
> change log entry that seems close is:
>
> - fix O_SYNC EIO error propagation through ext3/jbd (Stephen
> Tweedie)
>
> from kernel-2.4.21-34.EL. Is that anywhere close?

I kind of doubt it; as I said, I don't see anything in the changelogs
that looks immediately relevant...

-Eric

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 

Thread Tools




All times are GMT. The time now is 03:12 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org