Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760281AbYFML3H (ORCPT ); Fri, 13 Jun 2008 07:29:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755166AbYFML24 (ORCPT ); Fri, 13 Jun 2008 07:28:56 -0400 Received: from smtp-vbr3.xs4all.nl ([194.109.24.23]:3065 "EHLO smtp-vbr3.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755151AbYFML2z (ORCPT ); Fri, 13 Jun 2008 07:28:55 -0400 Subject: Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c From: Miquel van Smoorenburg To: Dave Chinner Cc: Oliver Pinter , lists@ku-gbr.de, linux-kernel@vger.kernel.org, Christoph Hellwig , xfs@oss.sgi.com, xfs-masters@oss.sgi.com, mikevs@xs4all.net In-Reply-To: <20080613030841.GC3700@disturbed> References: <20080612123031.21594jyk6rjc1lfk@imp.ku-gbr.de> <6101e8c40806120733m3c8647ccy149eb237e2c6d027@mail.gmail.com> <1213309629.29745.8.camel@localhost.localdomain> <20080613030841.GC3700@disturbed> Content-Type: text/plain Organization: XS4ALL Internet B.V. Date: Fri, 13 Jun 2008 13:28:38 +0200 Message-Id: <1213356518.8530.5.camel@n2o.xs4all.nl> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2159 Lines: 55 On Fri, 2008-06-13 at 13:08 +1000, Dave Chinner wrote: > On Fri, Jun 13, 2008 at 12:27:09AM +0200, Miquel van Smoorenburg wrote: > > On Thu, 2008-06-12 at 16:33 +0200, Oliver Pinter wrote: > > > add CC's > > > > > > On 6/12/08, lists@ku-gbr.de wrote: > > > > Hi! > > > > > > > > Today morning my server at home bailed out two times (reboot between): > > > > > > Jun 12 07:23:40 zappa > > > > Jun 12 07:23:40 zappa xfs_force_shutdown(sda7,0x8) called from line > > > > 1164 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff802f4d8a > > > > Jun 12 07:23:40 zappa Filesystem "sda7": Corruption of in-memory data > > > > detected. Shutting down filesystem: sda7 > > > > Jun 12 07:23:40 zappa Please umount the filesystem, and rectify the > > > > problem(s) > > > > Hmm, interesting. I'm seeing the same thing on one of my servers since I > > upgraded from 2.6.ancient (14 or so) to 2.6.25, while XFS otherwise has > > been very stable for me over the years: > > > > Linux transit5.news.xs4all.nl 2.6.25.6 #1 SMP Wed Jun 11 10:59:10 CEST > > 2008 x86_64 GNU/Linux > > > > Filesystem "sda4": XFS internal error xfs_trans_cancel at line 1163 of > > file fs/xfs/xfs_trans.c. Caller 0xffffffff880f1315 > > Pid: 3402, comm: diablo Not tainted 2.6.25.6 #1 > > This commit in 2.6.26 will probably fix it. > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=75de2a91c98a6f486f261c1367fe59f5583e15a3 "At ENOSPC, we can get a filesystem shutdown due to a cancelling a dirty transaction in xfs_mkdir or xfs_create." But: $ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 15G 5.1G 9.6G 35% /news The filesystem is only used for 35%. It might have hit 100% somewhere in the recent past though (a few reboots ago). I've applied the patch to 2.6.25.6 just in case, I'll let it run over the weekend to see what happens. Mike. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/