From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs and raid5 - "Structure needs cleaning for directory open"
Date: Mon, 10 May 2010 09:08:40 -0500 [thread overview]
Message-ID: <4BE81368.4030209@hardwarefreak.com> (raw)
In-Reply-To: <23944308.20100510122203@kaneda.iguw.tuwien.ac.at>
Rainer Fuegenstein put forth on 5/10/2010 5:22 AM:
> mark,
>
> yes, thank you, that looks very much like it. CentOS is still at 5.4,
> version 5.5 is long overdue :-(
Hi Rainer,
You don't have to wait for the next CentOS release. Just grab the source
for the latest stable kernel from kernel.org and roll your own. I've been
doing so for years with Debian stable in order to avoid problems such as
this one you've run into (that and security holes being plugged).
I'm running xfsprogs 2.9.8-1lenny1 that shipped with kernel 2.6.26 on top of
kernel 2.6.32.9 and haven't had any problems. At least, none so far with
mkfs.xfs, mount, xfs_db, or xfs_fsr. I've not had a need for xfs_check,
xfs_repair, or other xfs utils. My point being that older xfs tools seem to
work fine atop newer kernels.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-10 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 18:48 xfs and raid5 - "Structure needs cleaning for directory open" Rainer Fuegenstein
2010-05-09 19:07 ` Rainer Fuegenstein
2010-05-09 23:35 ` Rainer Fuegenstein
2010-05-10 2:20 ` Dave Chinner
2010-05-10 6:53 ` Mark Goodwin
2010-05-10 10:22 ` Re[2]: " Rainer Fuegenstein
2010-05-10 14:08 ` Stan Hoeppner [this message]
2010-05-17 21:28 ` Doug Ledford
2010-05-17 21:45 ` Dave Chinner
2010-05-17 22:18 ` Doug Ledford
2010-05-17 23:04 ` Dave Chinner
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=4BE81368.4030209@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