From: Eric Sandeen <sandeen@sandeen.net>
To: albert.graham@g-b.net
Cc: xfs@oss.sgi.com
Subject: Re: XFS Regression Issue in kernel 2.6.26.3
Date: Thu, 02 Oct 2008 15:46:12 -0500 [thread overview]
Message-ID: <48E53314.5010609@sandeen.net> (raw)
In-Reply-To: <48E51BF5.3080100@g-b.net>
Albert Graham wrote:
> Hi Guys,
>
> I use Fedora 8 as my MythTV backend server which uses XFS, ISince upgrading from kernel-2.6.25 to kernel-2.6.26 I've
> been getting the following errors (see below).
>
> This occurs on very light load (e.g. rsync from a remove server - via the internet), the only option is to reboot the
> server as the messages are constantly recursive once it starts.
>
> Now, I know my kernel it tainted with the NVIDIA driver and this is not a problem with any previous kernel.
>
> Please let me know if there is anything I can do to assist diagnosing this issue.
>
> Albert.
>
>
> =======================
> XFS internal error XFS_WANT_CORRUPTED_RETURN at line 280 of file fs/xfs/xfs_alloc.c. Caller 0xf88e0018
> Pid: 8025, comm: rsync Tainted: P 2.6.26.3-14.fc8PAE #1
> [<f8900a41>] xfs_error_report+0x2c/0x2e [xfs]
> [<f88de86c>] xfs_alloc_fixup_trees+0x264/0x273 [xfs]
> [<f88e0018>] ? xfs_alloc_ag_vextent_near+0x6e4/0x82b [xfs]
Do you know if the filesystem shows any corruption?
Try xfs_repair -n to see; if it is, getting an xfs_metadump prior to
repairing may help a post-mortem.
-Eric
next prev parent reply other threads:[~2008-10-02 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 19:07 XFS Regression Issue in kernel 2.6.26.3 Albert Graham
2008-10-02 20:46 ` Eric Sandeen [this message]
2008-10-02 23:52 ` Dave Chinner
2008-10-06 22:25 ` Albert Graham
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=48E53314.5010609@sandeen.net \
--to=sandeen@sandeen.net \
--cc=albert.graham@g-b.net \
--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