From: Dave Chinner <david@fromorbit.com>
To: DS <xfs@bob.dscon.sk>
Cc: xfs@oss.sgi.com
Subject: Re: xfs 2.6.31.9 error
Date: Tue, 29 Dec 2009 10:22:04 +1100 [thread overview]
Message-ID: <20091228232204.GB7613@discord.disaster> (raw)
In-Reply-To: <20091228151048.GA24031@bob.dscon.sk>
On Mon, Dec 28, 2009 at 04:10:48PM +0100, DS wrote:
> Hello,
>
> after upgrade from Debian etch -> Debian lenny with custom kernel
> 2.6.31.9 (before 2.6.28.1) I see this error and server is
> resetting sometimes..
>
> Filesystem was creating far far away (about 4years ago).
>
> XFS internal error XFS_WANT_CORRUPTED_RETURN at line 366 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff81169ae3
Any errors in the log before this (e.g. IO errors)?
> Pid: 4022, comm: procmail Not tainted 2.6.31.9 #3
> Call Trace:
> [<ffffffff8118edfe>] xfs_error_report+0x3e/0x40
> [<ffffffff811680fa>] xfs_alloc_fixup_trees+0x2ba/0x340
> [<ffffffff81167de9>] ? xfs_alloc_get_rec+0x29/0x60
> [<ffffffff81169ae3>] xfs_alloc_ag_vextent_near+0x3f3/0x940
> [<ffffffff8116a105>] xfs_alloc_ag_vextent+0xd5/0x130
> [<ffffffff8116aa68>] xfs_alloc_vextent+0x3a8/0x4f0
.....
Looks like a corrupted free space tree - that could have happened a
long time ago and only now are you tripping over it. I'd run
xfs_repair on the filesystem to fix up the problem. If it happens
again then we'll have to look deeper.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-28 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 15:10 xfs 2.6.31.9 error DS
2009-12-28 23:22 ` Dave Chinner [this message]
2010-01-06 9:02 ` xfs 2.6.31.9 error - possibly SOLVED DS
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=20091228232204.GB7613@discord.disaster \
--to=david@fromorbit.com \
--cc=xfs@bob.dscon.sk \
--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