From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n0ULuvDr054634 for ; Fri, 30 Jan 2009 15:56:58 -0600 Received: from mo-p05-ob.rzone.de (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id F23BA1894BCB for ; Fri, 30 Jan 2009 13:56:16 -0800 (PST) Received: from mo-p05-ob.rzone.de (mo-p05-ob.rzone.de [81.169.146.181]) by cuda.sgi.com with ESMTP id pdrNqYVDEbKnvgyN for ; Fri, 30 Jan 2009 13:56:16 -0800 (PST) Received: from [10.1.1.65] ([213.39.240.61]) by post.strato.de (mrclete mo46) (RZmta 18.15) with ESMTP id D00a04l0UKAQDv for ; Fri, 30 Jan 2009 22:54:18 +0100 (MET) Message-ID: <498376CF.8020806@renderforce.de> Date: Fri, 30 Jan 2009 22:53:19 +0100 From: Steffen Knauf MIME-Version: 1.0 Subject: xfs_force_shutdown after Raid crash Reply-To: steffen.knauf@renderforce.de List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com Hello, after a raid crash (Raid Controller problem, 3 Disks of the Disk Group were kicked out oft the diskgroup), 2 of 3 partitions (XFS FS) were shutdown immediately. Perhaps somebody has a idea, what's the best solution (xfs_repair?). here a small output of the logfile: ------------------------------------------------------------------------------------------ kernel: Call Trace: {:xfs:xfs_free_ag_extent+1081} kernel: {:xfs:xfs_free_extent+186} {:xfs:xfs_efd_init+54} kernel: {:xfs:xfs_trans_get_efd+36} {:xfs:xfs_bmap_finish+240} kernel: {:xfs:xfs_itruncate_finish+365} {:xfs:xfs_inactive+558} kernel: {:xfs:validate_fields+39} {:xfs:linvfs_clear_inode+165} kernel: {clear_inode+210} {generic_delete_inode+231} kernel: {do_unlinkat+213} {system_call+126} kernel: xfs_force_shutdown(sdb2,0x8) called from line 4200 of file fs/xfs/xfs_bmap.c. Return address = 0xffffffff882d26e7 kernel: Filesystem "sdb2": Corruption of in-memory data detected. Shutting down filesystem: sdb2 kernel: Please umount the filesystem, and rectify the problem(s) kernel: XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff882c5b35 munich kernel: munich kernel: Call Trace: {:xfs:xfs_alloc_fixup_trees+700} munich kernel: {:xfs:xfs_btree_init_cursor+49} {:xfs:xfs_alloc_ag_vextent+3015} munich kernel: {__down_read+18} {:xfs:xfs_alloc_vextent+719} munich kernel: {:xfs:xfs_bmapi+5590} {:xfs:xlog_write+1518} munich kernel: {:xfs:kmem_zone_zalloc+30} {:xfs:xfs_iomap_write_allocate+521} munich kernel: {mempool_alloc+49} {:xfs:xfs_iomap+762} munich kernel: {:xfs:xfs_map_blocks+53} {alternate_node_alloc+112} munich kernel: {:xfs:xfs_page_state_convert+695} munich kernel: {alternate_node_alloc+112} {cfq_set_request+619} munich kernel: {swiotlb_map_sg+55} {:mptscsih:mptscsih_qcmd+1399} munich kernel: {:xfs:linvfs_writepage+167} {mpage_writepages+435} munich kernel: {:xfs:linvfs_writepage+0} {generic_make_request+339} munich kernel: {submit_bio+186} {do_writepages+41} munich kernel: {__writeback_single_inode+449} {default_wake_function+0} munich kernel: {:xfs:xfs_bdstrat_cb+55} {:xfs:xfs_log_need_covered+82} munich kernel: {sync_sb_inodes+469} {keventd_create_kthread+0} munich kernel: {writeback_inodes+130} {wb_kupdate+218} munich kernel: {thread_return+0} {pdflush+0} munich kernel: {pdflush+366} {wb_kupdate+0} munich kernel: {kthread+236} {child_rip+8} munich kernel: {keventd_create_kthread+0} {kthread+0} munich kernel: {child_rip+0} ------------------------------------------------------------------------------------------ greets Steffen _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs