From: Andreas Kotes <count-linux@flatline.de>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS internal error
Date: Mon, 10 Mar 2008 13:22:16 +0100 [thread overview]
Message-ID: <20080310122216.GG14256@slop.flatline.de> (raw)
In-Reply-To: <20071008001452.GX995458@sgi.com>
Hello,
* David Chinner <dgc@sgi.com> [20080310 13:18]:
> Yes, but those previous corruptions get left on disk as a landmine
> for you to trip over some time later, even on a kernel that has the
> bug fixed.
>
> I suggest that you run xfs_check on the filesystem and if that
> shows up errors, run xfs_repair onteh filesystem to correct them.
I seem to be having similiar problems, and xfs_repair is not helping :(
I always run into:
[ 137.099267] Filesystem "sda2": XFS internal error xfs_trans_cancel at line 1132 of file fs/xfs/xfs_trans.c. Caller 0xffffffff80372156
[ 137.106267]
[ 137.106268] Call Trace:
[ 137.113129] [<ffffffff803692f0>] xfs_trans_cancel+0x100/0x130
[ 137.116524] [<ffffffff80372156>] xfs_create+0x256/0x6e0
[ 137.119904] [<ffffffff80341e09>] xfs_dir2_isleaf+0x19/0x50
[ 137.123269] [<ffffffff8037e145>] xfs_vn_mknod+0x195/0x250
[ 137.126607] [<ffffffff8028f32c>] vfs_create+0xac/0xf0
[ 137.129920] [<ffffffff80292b3c>] open_namei+0x5dc/0x700
[ 137.133227] [<ffffffff8022a443>] __wake_up+0x43/0x70
[ 137.136477] [<ffffffff802851bc>] do_filp_open+0x1c/0x50
[ 137.139693] [<ffffffff8028524a>] do_sys_open+0x5a/0x100
[ 137.142838] [<ffffffff80220a83>] sysenter_do_call+0x1b/0x67
[ 137.145964]
[ 137.149014] xfs_force_shutdown(sda2,0x8) called from line 1133 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff8036930e
[ 137.163485] Filesystem "sda2": Corruption of in-memory data detected. Shutting down filesystem: sda2
directly after booting.
I'm using kernel 2.6.22.16 and xfs_repair version 2.9.7
How can I help finding the problem? I'd like xfs_repair to be able to
fix this.
Br,
Andreas
--
flatline IT services - Andreas Kotes - Tailored solutions for your IT needs
next prev parent reply other threads:[~2008-03-10 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 1:09 XFS internal error Max Waterman
2007-10-08 0:14 ` David Chinner
2007-10-08 1:54 ` Max Waterman
2007-10-08 2:32 ` Barry Naujok
2007-10-08 2:48 ` Max Waterman
2008-03-10 12:22 ` Andreas Kotes [this message]
2008-03-10 22:30 ` David Chinner
2008-03-10 22:59 ` Andreas Kotes
2008-03-10 23:45 ` David Chinner
2008-03-11 13:47 ` Andreas Kotes
-- strict thread matches above, loose matches on Subject: below --
2006-08-26 16:06 Gerardo Exequiel Pozzi
2006-08-26 17:05 ` Jeffrey Hundstad
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=20080310122216.GG14256@slop.flatline.de \
--to=count-linux@flatline.de \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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