From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Sun, 10 Sep 2006 07:38:50 -0700 (PDT) Received: from rapidforum.com (www.rapidforum.com [80.237.244.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id k8AEcgDW020904 for ; Sun, 10 Sep 2006 07:38:43 -0700 Message-ID: <4504151F.6050704@rapidforum.com> Date: Sun, 10 Sep 2006 15:37:35 +0200 From: Christian Schmid MIME-Version: 1.0 Subject: Critical xfs bug in 2.6.17.11? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: xfs@oss.sgi.com Hello. Instead of a tmpfs, I use a raid 10 softraid. Unfortunately it crashed after 10 hours of extreme activities (read/block-writes with up to 250 streams/deletes) 12 gb memory-test successful. 2 cpu xeon smp system. Tell me if this helps you: Sep 9 18:08:49 inode430 kernel: [87433.143498] 0x0: 58 41 47 46 00 00 00 01 00 00 00 00 00 04 34 a0 Sep 9 18:08:49 inode430 kernel: [87433.143672] Filesystem "md5": XFS internal error xfs_alloc_read_agf at line 2176 of file fs/xfs/xfs_alloc.c. Caller 0xfffffff f80314069 Sep 9 18:08:49 inode430 kernel: [87433.143904] Sep 9 18:08:49 inode430 kernel: [87433.143905] Call Trace: {xfs_corruption_error+244} Sep 9 18:08:49 inode430 kernel: [87433.143995] {xfs_iext_insert+65} {xfs_trans_read_buf+203} Sep 9 18:08:49 inode430 kernel: [87433.144353] {xfs_alloc_read_agf+281} {xfs_alloc_fix_freelist+356} Sep 9 18:08:49 inode430 kernel: [87433.144628] {xfs_alloc_fix_freelist+356} {__down_read+18} Sep 9 18:08:49 inode430 kernel: [87433.144855] {xfs_alloc_vextent+289} {xfs_bmapi+4061} Sep 9 18:08:49 inode430 kernel: [87433.145091] {xfs_bmap_search_multi_extents+175} Sep 9 18:08:49 inode430 kernel: [87433.145226] {xfs_iomap_write_allocate+675} {xfs_iomap+701} Sep 9 18:08:49 inode430 kernel: [87433.145473] {generic_make_request+515} {xfs_map_blocks+67} Sep 9 18:08:49 inode430 kernel: [87433.145846] {xfs_page_state_convert+722} {xfs_vm_writepage+179} Sep 9 18:08:49 inode430 kernel: [87433.146079] {mpage_writepages+459} {xfs_vm_writepage+0} Sep 9 18:08:49 inode430 kernel: [87433.146330] {do_writepages+41} {__writeback_single_inode+559} Sep 9 18:08:49 inode430 kernel: [87433.146583] {default_wake_function+0} {default_wake_function+0} Sep 9 18:08:49 inode430 kernel: [87433.146847] {xfs_trans_first_ail+28} {sync_sb_inodes+501} Sep 9 18:08:49 inode430 kernel: [87433.147230] {keventd_create_kthread+0} {writeback_inodes+144} Sep 9 18:08:49 inode430 kernel: [87433.147463] {wb_kupdate+148} {pdflush+313} Sep 9 18:08:49 inode430 kernel: [87433.147825] {wb_kupdate+0} {pdflush+0} Sep 9 18:08:49 inode430 kernel: [87433.148142] {kthread+218} {child_rip+8} Sep 9 18:08:49 inode430 kernel: [87433.148420] {keventd_create_kthread+0} {kthread+0} Sep 9 18:08:49 inode430 kernel: [87433.148775] {child_rip+0} Sep 9 18:08:49 inode430 kernel: [87433.149105] Filesystem "md5": XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c. Caller 0xffffffff8 0349bf8 Sep 9 18:08:49 inode430 kernel: [87433.149262] Sep 9 18:08:49 inode430 kernel: [87433.149263] Call Trace: {xfs_trans_cancel+111} Sep 9 18:08:49 inode430 kernel: [87433.149348] {xfs_iomap_write_allocate+1006} {xfs_iomap+701} Sep 9 18:08:49 inode430 kernel: [87433.149568] {generic_make_request+515} {xfs_map_blocks+67} Sep 9 18:08:49 inode430 kernel: [87433.149847] {xfs_page_state_convert+722} {xfs_vm_writepage+179} Sep 9 18:08:49 inode430 kernel: [87433.150169] {mpage_writepages+459} {xfs_vm_writepage+0} Sep 9 18:08:49 inode430 kernel: [87433.150435] {do_writepages+41} {__writeback_single_inode+559} Sep 9 18:08:49 inode430 kernel: [87433.150593] {default_wake_function+0} {default_wake_function+0} Sep 9 18:08:49 inode430 kernel: [87433.150807] {xfs_trans_first_ail+28} {sync_sb_inodes+501} Sep 9 18:08:49 inode430 kernel: [87433.151042] {keventd_create_kthread+0} {writeback_inodes+144} Sep 9 18:08:49 inode430 kernel: [87433.151271] {wb_kupdate+148} {pdflush+313} Sep 9 18:08:49 inode430 kernel: [87433.151439] {wb_kupdate+0} {pdflush+0} Sep 9 18:08:49 inode430 kernel: [87433.151680] {kthread+218} {child_rip+8} Sep 9 18:08:49 inode430 kernel: [87433.151922] {keventd_create_kthread+0} {kthread+0} Sep 9 18:08:49 inode430 kernel: [87433.152086] {child_rip+0} Sep 9 18:08:49 inode430 kernel: [87433.152489] xfs_force_shutdown(md5,0x8) called from line 1151 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff80357507 Sep 9 18:08:49 inode430 kernel: [87433.168623] Filesystem "md5": Corruption of in-memory data detected. Shutting down filesystem: md5 Sep 9 18:08:49 inode430 kernel: [87433.168903] Please umount the filesystem, and rectify the problem(s)