From: Eric Sandeen <sandeen@sandeen.net>
To: Drew Wareham <m3rlin@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check segfault / xfs_repair I/O error
Date: Fri, 20 Apr 2012 12:01:36 -0500 [thread overview]
Message-ID: <4F919670.3090603@sandeen.net> (raw)
In-Reply-To: <CALcU-6i3MY+Z-dFzE5p34DSMxcQi2dPdXZHenh+=5TObyiB8eQ@mail.gmail.com>
On 4/20/12 10:46 AM, Drew Wareham wrote:
> Good point! We're running CentOS 5, so is the CentOS-Plus repo the way to go? These servers are all setup from a fairly old base image hence using kmod-xfs, definitely something I'll address.
as long as you're on x86_64, the stock kernel has the xfs.ko you want.
I'm not big on offering too much centos support, but i would rather not see people using reaaaly crufty xfs. :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-20 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 13:15 xfs_check segfault / xfs_repair I/O error Drew Wareham
2012-04-15 19:47 ` Stan Hoeppner
2012-04-15 22:31 ` Dave Chinner
2012-04-16 10:18 ` Stan Hoeppner
2012-04-20 4:11 ` Drew Wareham
2012-04-20 15:06 ` Eric Sandeen
2012-04-20 15:46 ` Drew Wareham
2012-04-20 17:01 ` Eric Sandeen [this message]
2012-04-21 0:57 ` Drew Wareham
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=4F919670.3090603@sandeen.net \
--to=sandeen@sandeen.net \
--cc=m3rlin@gmail.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