Ocfs2 users - Dec 2007 - Badness in __remove_from_page_cache and page_remove_rmap

We have freshly installed cluster with SLES9 x86_64 + updates.

We are seeing big bunch of these errors on one node, but we can't tell
what's
their effect.

The hardware is Dell PowerEdge 6850, quite new.  Can hardware be a suspect?

Linux node3-cluster1 2.6.5-7.287.3-smp #1 SMP Tue Oct 2 07:31:36 UTC 2007 
x86_64 x86_64 x86_64 GNU/Linux





Dec  9 09:26:28 node3-cluster1 kernel: Badness in __remove_from_page_cache at 
mm/filemap.c:110
Dec  9 09:26:28 node3-cluster1 kernel:
Dec  9 09:26:28 node3-cluster1 kernel: Call 
Trace:<ffffffff80168e5d>{__remove_from_page_cache+125} 
<ffffffff80168f24>{remove_from_page_cach
e+68}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffff80171aaa>{truncate_complete_page+58} 
<ffffffff80171bd3>{truncate_inode_pages+147}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa0489eb8>{:ocfs2:ocfs2_data_convert_worker+264}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa0489db0>{:ocfs2:ocfs2_data_convert_worker+0}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa0485d02>{:ocfs2:ocfs2_generic_unblock_lock+370}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa048605d>{:ocfs2:ocfs2_unblock_data+253} 
<ffffffffa04824f9>{:ocfs2:ocfs2_process_blo
cked_lock+297}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa04b3393>{:ocfs2:ocfs2_vote_thread+531} 
<ffffffff8013d620>{autoremove_wake_function+
0}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffff80133f10>{__wake_up_common+64} 
<ffffffff8013d620>{autoremove_wake_function+0}
Dec  9 09:26:28 node3-cluster1 kernel:        
<ffffffffa04b3180>{:ocfs2:ocfs2_vote_thread+0} 
<ffffffff80153683>{kthread+243}
Dec  9 09:26:28 node3-cluster1 kernel:       
<ffffffff8011122f>{child_rip+8}
<ffffffff80153510>{keventd_create_kthread+0}
Dec  9 09:26:28 node3-cluster1 kernel:       
<ffffffff80153590>{kthread+0}
<ffffffff80111227>{child_rip+0}
Dec  9 09:26:28 node3-cluster1 kernel:
Dec  9 09:26:49 node3-cluster1 kernel: Badness in page_remove_rmap at 
mm/objrmap.c:383
Dec  9 09:26:49 node3-cluster1 kernel:
Dec  9 09:26:49 node3-cluster1 kernel: Call 
Trace:<ffffffff801808ef>{page_remove_rmap+223} 
<ffffffff80177ae1>{unmap_vmas+1185}
Dec  9 09:26:49 node3-cluster1 kernel:        
<ffffffff80135e00>{default_wake_function+0}
<ffffffff8017c1dc>{do_munmap+556}
Dec  9 09:26:49 node3-cluster1 kernel:        
<ffffffff8017c968>{sys_munmap+72}
<ffffffff801106b4>{system_call+124}
Dec  9 09:26:49 node3-cluster1 kernel:
Dec  9 09:26:49 node3-cluster1 kernel: Badness in page_remove_rmap at 
mm/objrmap.c:383
Dec  9 09:26:49 node3-cluster1 kernel:
Dec  9 09:26:49 node3-cluster1 kernel: Call 
Trace:<ffffffff801808ef>{page_remove_rmap+223} 
<ffffffff80177ae1>{unmap_vmas+1185}
Dec  9 09:26:49 node3-cluster1 kernel:        
<ffffffff80135e00>{default_wake_function+0}
<ffffffff8017c1dc>{do_munmap+556}
Dec  9 09:26:49 node3-cluster1 kernel:        
<ffffffff8017c968>{sys_munmap+72}
<ffffffff801106b4>{system_call+124}
Dec  9 09:26:49 node3-cluster1 kernel:



Thanks

On Sunday 09 December 2007 02:00:17 pm Silviu Marin-Caea
wrote:
> We have freshly installed cluster with SLES9 x86_64 + updates.
>
> We are seeing big bunch of these errors on one node, but we can't tell
> what's their effect.
>
> The hardware is Dell PowerEdge 6850, quite new.  Can hardware be a suspect?
>
> Linux node3-cluster1 2.6.5-7.287.3-smp #1 SMP Tue Oct 2 07:31:36 UTC 2007
> x86_64 x86_64 x86_64 GNU/Linux
It appeared at reboot on the second node too, so hardware is unlikely to be 
faulty.