From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n2RKNcx7006134 for ; Fri, 27 Mar 2009 15:23:48 -0500 Received: from mx2.redhat.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id AF4ED1CE30E for ; Fri, 27 Mar 2009 13:23:11 -0700 (PDT) Received: from mx2.redhat.com (mx2.redhat.com [66.187.237.31]) by cuda.sgi.com with ESMTP id igsZg37crIjshEAJ for ; Fri, 27 Mar 2009 13:23:11 -0700 (PDT) Message-ID: <49CD359E.905@sandeen.net> Date: Fri, 27 Mar 2009 15:22:54 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: Corruption of in-memory data References: <49CD2EF0.9060009@blackopscode.com> In-Reply-To: <49CD2EF0.9060009@blackopscode.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Florian Hines Cc: xfs@oss.sgi.com Florian Hines wrote: > Hey everybody, > > Over the last few day's I've been getting a rash (8 so far) of disk's > throwing the error "Filesystem "sdxX": Corruption of in-memory data > detected. Shutting down filesystem: sdxX". xfs_check never seem's to > find anything and just unmounting and remounting solves the issue at > least for awhile. try xfs_repair, with -n if you want a dry run. It's canceling a dirty transaction, I'm not sure why. The message is a little misleading. Want to try 2.6.29? :) -Eric > Is this usually caused by bad ram ? It's happened > on 6 systems so far (all using Debian Etch AMD64 with the stock 2.6.18 > kernel, each system as a 5 sata drives, not raided). > > Can anyone shed some light on what this error actually indicates for me ? > > --Full error from dmesg below-- > Filesystem "sda3": XFS internal error xfs_trans_cancel at line 1138 of > file fs/xfs/xfs_trans.c. Caller 0xffffffff8818ead5 > > Call Trace: > [] :xfs:xfs_trans_cancel+0x5b/0xfe > [] :xfs:xfs_rename+0xa13/0xa9a > [] :xfs:xfs_vn_rename+0x2c/0x6f > [] __up_read+0x13/0x8a > [] :xfs:xfs_iunlock+0x57/0x79 > [] __up_read+0x13/0x8a > [] :xfs:xfs_iunlock+0x57/0x79 > [] :xfs:xfs_access+0x3d/0x46 > [] vfs_rename+0x2d5/0x426 > [] sys_renameat+0x180/0x1f9 > [] sys_newstat+0x28/0x31 > [] system_call+0x7e/0x83 > > xfs_force_shutdown(sda3,0x8) called from line 1139 of file > fs/xfs/xfs_trans.c. Return address = 0xffffffff8818fdee > Filesystem "sda3": Corruption of in-memory data detected. Shutting down > filesystem: sda3 > Please umount the filesystem, and rectify the problem(s) > > > -- > flo > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs