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 10:06:31 -0500 [thread overview]
Message-ID: <4F917B77.6040403@sandeen.net> (raw)
In-Reply-To: <CALcU-6goaENFYsvUxz3yQD=w6ipmHuo-GxoRHT1GaQ6+yW5-pA@mail.gmail.com>
On 4/15/12 8:15 AM, Drew Wareham wrote:
> Hello Everyone,
>
> Hopefully this is the correct kind of information to send to this list.
>
> I have an issue with a large XFS volume (17TB) that mounts, but is not readable. I can view the folder structure on the volume but I can't access any of the actual data. A disk failed in a RAID5 array and while it has rebuilt now, it looks like it's caused serious data integrity issues.
>
> Here is the CentOS release / Kernel version:
> [root@svr608 ~]# uname -a
> Linux svr608 2.6.18-308.1.1.el5 #1 SMP Wed Mar 7 04:16:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
> [root@svr608 ~]# cat /etc/redhat-release
> CentOS release 5.8 (Final)
> [root@svr608 ~]# cat /tmp/yum.list | grep xfs | grep installed
> kmod-xfs.x86_64 0.4-2 installed
You reall, Really, REALLY, *REALLY* want to remove kmod-xfs.
RHEL5 has been shipping with supported xfs for what, 2 years now, and that old kmod-xfs
is an ancient, ancient piece of unmaintained, bitrotting code. Sadly it overrides
the kernel rpm's xfs.ko. I don't know if this is the root cause of your problem; probably
not, but eventually it will likely be the root cause of some other problem :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-20 15:06 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 [this message]
2012-04-20 15:46 ` Drew Wareham
2012-04-20 17:01 ` Eric Sandeen
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=4F917B77.6040403@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.