xfs
[Top] [All Lists]

Re: Did you ever get that memory situation straightened out?

To: GBanschbach@xxxxxxxxxxx
Subject: Re: Did you ever get that memory situation straightened out?
From: Jim Eshleman <jce0@xxxxxxxxxx>
Date: Tue, 07 May 2002 13:28:55 -0400
Cc: linux-xfs@xxxxxxxxxxx
References: <OF4F4AF6C0.842D06C5-ON85256BB1.0073A389@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
Dear Jim,

     I read your posting from last Nov about the 64GB patch on
2.4.13 and .14.    Does it all work now ?   I am interested in knowing
more about your experiences....
Sincerely,

Greg

Greg (cc: linux-xfs)

Wow, that seems like a long time ago. Sorry for not posting an update. Since then I've run 2.4.1[678] with xfs from split patches and CVS. The last was 2.4.18+split patches+an nfs patch that Steve? posted to the list. That resulted in ~35 days uptime before hanging with the oops appended below. I'm now running 2.4.19-pre6aa1 (which includes xfs of around Mar 30 timeframe I think) and a patched ips (IBM serveraid) driver which does highmem io, and have been up for 10 days.

Note this is a very busy 8-way 8G campus mail server. The 2.4 kernel and xfs have been steadily improving. I think I can say now that yes, it does all work. I don't know how soon I'll get to see triple-digit uptime but I'm optimistic.

Jim

Apr 27 09:44:16 xxxx kernel: invalid operand: 0000
Apr 27 09:44:16 xxxx kernel: CPU:    5
Apr 27 09:44:16 xxxx kernel: EIP: 0010:[ll_rw_block+138/504] Not tainted
Apr 27 09:44:16 xxxx kernel: EIP:    0010:[<c022cd7e>]    Not tainted
Apr 27 09:44:16 xxxx kernel: EFLAGS: 00010287
Apr 27 09:44:16 xxxx kernel: eax: 00000000 ebx: 00003a04 ecx: df6b4ba0 edx: 00000000 Apr 27 09:44:16 xxxx kernel: esi: 00000000 edi: e4e6fd28 ebp: 00000200 esp: e4e6fce0
Apr 27 09:44:16 xxxx kernel: ds: 0018   es: 0018   ss: 0018
Apr 27 09:44:16 xxxx kernel: Process procmail (pid: 14699, stackpage=e4e6f000) Apr 27 09:44:16 xxxx kernel: Stack: e9f051e0 df6b4ba0 e4e6fd4c 00000000 df6b4ba0 00000000 00001000 00000200 Apr 27 09:44:16 xxxx kernel: df6b4ba0 c0139685 00000001 00000001 e4e6fd28 e9f051c0 c9d873e0 c9d873c8 Apr 27 09:44:16 xxxx kernel: 00000001 e4e6fd4c df6b4ba0 f7192e80 00000001 f6d00000 00000000 00000292 Apr 27 09:44:16 xxxx kernel: Call Trace: [fsync_inode_data_buffers+165/384] [xfs_mod_incore_sb_batch+71/160] [xfs_trans_unreserve_and_mod_sb+348/360] [xfs_log_notify+54/84] [__refile_buffer+84/92] Apr 27 09:44:16 xxxx kernel: Call Trace: [<c0139685>] [<c01ed267>] [<c01f1410>] [<c01e411e>] [<c0139a9c>] Apr 27 09:44:16 xxxx kernel: [refile_buffer+23/36] [set_buffer_dirty_uptodate+51/68] [__pb_block_commit_write_async+46/80] [pagebuf_commit_write+66/144] [pagebuf_commit_write+115/144] [pagebuf_generic_file_write+677/792] Apr 27 09:44:16 xxxx kernel: [<c0139abb>] [<c0201927>] [<c0201cd6>] [<c0200b02>] [<c0200b33>] [<c02023f5>] Apr 27 09:44:16 xxxx kernel: [pagebuf_generic_file_write+727/792] [xfs_trans_unlocked_item+34/60] [xfs_trans_unlocked_item+34/60] [xfs_iunlock+75/84] [xfs_rwunlock+48/100] [xfs_write+1276/1292] Apr 27 09:44:16 xxxx kernel: [<c0202427>] [<c01f1e62>] [<c01f1e62>] [<c01dcfcb>] [<c01fb934>] [<c0207860>] Apr 27 09:44:16 xxxx kernel: [pagebuf_flush+23/40] [fs_flush_pages+41/48] [xfs_fsync+239/748] [linvfs_fsync+65/76] [sys_fsync+98/172] [system_call+51/56] Apr 27 09:44:16 xxxx kernel: [<c0200b67>] [<c02038a1>] [<c01f6f27>] [<c0203449>] [<c0138e26>] [<c01070eb>]
Apr 27 09:44:16 xxxx kernel:
Apr 27 09:44:16 xxxx kernel: Code: 0f 0b 83 c7 04 46 3b 74 24 2c 7c c8 8b 4c 24 28 f6 c1 01 74
Apr 27 09:44:48 xxxx kernel:  invalid operand: 0000
Apr 27 09:44:48 xxxx kernel: CPU:    3
Apr 27 09:44:48 xxxx kernel: EIP: 0010:[__make_request+141/1652] Not tainted
Apr 27 09:44:48 xxxx kernel: EIP:    0010:[<c022c58d>]    Not tainted
Apr 27 09:44:48 xxxx kernel: EFLAGS: 00010246
Apr 27 09:44:48 xxxx kernel: eax: 00000008 ebx: 00000841 ecx: 00000001 edx: 00000004 Apr 27 09:44:48 xxxx kernel: esi: ed969480 edi: 00004000 ebp: 00000000 esp: c9897eac
Apr 27 09:44:48 xxxx kernel: ds: 0018   es: 0018   ss: 0018
Apr 27 09:44:48 xxxx kernel: Process kupdated (pid: 13, stackpage=c9897000)
Apr 27 09:44:48 xxxx kernel: Stack: 00000841 ed969480 c03e66c0 00000000 f7159b70 f7159a00 00004000 c9978498 Apr 27 09:44:48 xxxx kernel: c9978490 00000400 00000000 00000000 00000008 002007d0 00000001 c022cc12 Apr 27 09:44:48 xxxx kernel: c9978478 00000001 ed969480 00000008 00000001 eb770ec0 00000051 c022ccd8 Apr 27 09:44:48 xxxx kernel: Call Trace: [generic_make_request+158/292] [submit_bh+64/92] [write_locked_buffers+32/44] [write_some_buffers+204/280] [sync_old_buffers+91/148] Apr 27 09:44:48 xxxx kernel: Call Trace: [<c022cc12>] [<c022ccd8>] [<c0138944>] [<c0138a1c>] [<c013bf77>] Apr 27 09:44:48 xxxx kernel: [kupdate+317/324] [stext+0/68] [kernel_thread+26/48] [kernel_thread+35/48] Apr 27 09:44:48 xxxx kernel: [<c013c285>] [<c0105000>] [<c01057d2>] [<c01057db>]
Apr 27 09:44:48 xxxx kernel:
Apr 27 09:44:48 xxxx kernel: Code: 0f 0b 56 8b 7c 24 48 57 e8 d2 92 f0 ff 89 c6 83 c4 08 0f b6


<Prev in Thread] Current Thread [Next in Thread>
  • Re: Did you ever get that memory situation straightened out?, Jim Eshleman <=