public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO)
Date: Tue, 06 Jul 2010 11:17:58 -0500	[thread overview]
Message-ID: <4C335736.1070701@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTimKKEvfJx6EQZeQF_HnlBLj6B8Kjfy6jUHGPnz5@mail.gmail.com>

Shaun Adolphson put forth on 7/6/2010 5:57 AM:

> Software:
> - Fresh install of CentOS 5.5 64bit all patches up to date
> - Kernel 2.6.18-194.3.1.el5.centos.plus

First thing that comes to mind is the fact that 2.6.18 is about 3 years old.
I'm not familiar with CentOS patching policies, but even if you've received
and applied some XFS patches, they'd still probably be rather old.

If CentOS 5.5 doesn't have a much newer kernel package available, say 2.6.30
or later, if I were you, I'd grab the kernel source from kernel.org and roll
your own 2.6.33.6 or 2.6.34.1.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-07-06 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 10:57 CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO) Shaun Adolphson
2010-07-06 16:17 ` Stan Hoeppner [this message]
2010-07-06 22:00 ` Shaun Adolphson
2010-07-06 23:18 ` Dave Chinner
2010-07-07  1:51   ` Eric Sandeen
2010-07-08 11:21   ` Shaun Adolphson
2010-07-11 11:44     ` Shaun Adolphson
2010-07-11 11:47       ` Shaun Adolphson
2010-07-12  1:08       ` Dave Chinner
2010-07-12  5:45         ` Dave Chinner
2010-08-16 10:32           ` Shaun Adolphson

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=4C335736.1070701@hardwarefreak.com \
    --to=stan@hardwarefreak.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