From: Miquel van Smoorenburg <mikevs@xs4all.net>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: lists@ku-gbr.de, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com, xfs-masters@oss.sgi.com, mikevs@xs4all.net
Subject: Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c
Date: Fri, 13 Jun 2008 00:27:09 +0200 [thread overview]
Message-ID: <1213309629.29745.8.camel@localhost.localdomain> (raw)
In-Reply-To: <6101e8c40806120733m3c8647ccy149eb237e2c6d027@mail.gmail.com>
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
Call Trace:
[<ffffffff880f1315>] :xfs:xfs_create+0x1e5/0x520
[<ffffffff880ea4a6>] :xfs:xfs_trans_cancel+0x126/0x150
[<ffffffff880f1315>] :xfs:xfs_create+0x1e5/0x520
[<ffffffff880fcb79>] :xfs:xfs_vn_mknod+0x1d9/0x320
[<ffffffff8028811c>] vfs_create+0xac/0xf0
[<ffffffff8028b6bd>] open_namei+0x61d/0x6c0
[<ffffffff802448c0>] autoremove_wake_function+0x0/0x30
[<ffffffff8027da0c>] do_filp_open+0x1c/0x50
[<ffffffff8027d6e9>] get_unused_fd_flags+0x79/0x120
[<ffffffff8027da9a>] do_sys_open+0x5a/0xf0
[<ffffffff8020b2bb>] system_call_after_swapgs+0x7b/0x80
xfs_force_shutdown(sda4,0x8) called from line 1164 of file
fs/xfs/xfs_trans.c. Return address = 0xffffffff880ea4bf
Filesystem "sda4": Corruption of in-memory data detected. Shutting down
filesystem: sda4
Please umount the filesystem, and rectify the problem(s)
After a reboot, xfs_repair didn't find anything wrong with the fs. It
has happened 3 times over the last few days already.
FS is on a local SCSI raid (dpt_i2o), not SATA.
Mike.
next prev parent reply other threads:[~2008-06-12 22:27 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 [this message]
2008-06-13 3:08 ` Dave Chinner
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=1213309629.29745.8.camel@localhost.localdomain \
--to=mikevs@xs4all.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@ku-gbr.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox