All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Miquel van Smoorenburg <mikevs@xs4all.net>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
	lists@ku-gbr.de, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	xfs@oss.sgi.com, xfs-masters@oss.sgi.com
Subject: Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c
Date: Fri, 13 Jun 2008 13:08:41 +1000	[thread overview]
Message-ID: <20080613030841.GC3700@disturbed> (raw)
In-Reply-To: <1213309629.29745.8.camel@localhost.localdomain>

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 <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

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-06-13  3:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 10:30 XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c lists
2008-06-12 14:33 ` Oliver Pinter
2008-06-12 22:24   ` [xfs-masters] " Eric Sandeen
2008-06-13  7:15     ` Konstantin Kletschke
2008-06-12 22:27   ` Miquel van Smoorenburg
2008-06-13  3:08     ` Dave Chinner [this message]
2008-06-13  7:24       ` Konstantin Kletschke
2008-06-13 15:36         ` [xfs-masters] " Dave Chinner
2008-06-13 11:28       ` Miquel van Smoorenburg
2008-06-16 15:50         ` Miquel van Smoorenburg
2008-06-17  5:31           ` Dave Chinner
2008-06-20  5:27       ` Konstantin Kletschke
2008-06-20  5:45         ` Konstantin Kletschke
2008-06-22 22:53         ` Dave Chinner
2008-06-23  7:58           ` Konstantin Kletschke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080613030841.GC3700@disturbed \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@ku-gbr.de \
    --cc=mikevs@xs4all.net \
    --cc=oliver.pntr@gmail.com \
    --cc=xfs-masters@oss.sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.