From: "Christian J. Dietrich" <dietrich@internet-sicherheit.de>
To: xfs@oss.sgi.com
Subject: Repeated XFS corruption on RAID-10 on Adaptec 51245
Date: Fri, 08 Jun 2012 11:45:28 +0200 [thread overview]
Message-ID: <4FD1C9B8.70907@internet-sicherheit.de> (raw)
Hey all,
I have problems with an XFS volume. Upon discovering the message
"kernel: XFS (sda3): corrupt inode 3714097 (bad size 16437 for local
fork, size = 60)."
I ran xfs_repair /dev/sda3 (/dev/sda3 was unmounted). It reported to
have fixed some errors.
However, after a while in normal operation, another XFS corruption
occurred on /dev/sda3. I noticed that repeatedly calling xfs_repair will
always report and fix new errors, even if the volume is not mounted in
between, e.g., "rebuilding directory inode XXX" with different (new)
values of XXX.
/dev/sda is a 12 TB RAID-10 volume on an Adaptec 51245 controller. All
disks are online and none is reported faulty.
Naive, I would assume that running xfs_repair once would fix all errors.
My guess is that the underlying RAID volume (Adaptec 51245 RAID 10) is
somehow invalid (although I can not find any indicators confirming
this). Any suggestions?
I am running CentOS 6.2 (=RHEL 6.2) with kernel
2.6.32-220.17.1.el6.x86_64 (most recent) and all OS updates installed.
Controller Firmware is the most recent (18948), driver version is 1.1-5.
HDDs are 2x WD2001FASS, 10x WD2002FAEX.
Thanks in advance,
Chris
--
Christian J. Dietrich
Institute for Internet Security - if(is)
Westfälische Hochschule University of Applied Sciences
https://www.internet-sicherheit.de
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-06-08 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 9:45 Christian J. Dietrich [this message]
2012-06-08 10:51 ` Repeated XFS corruption on RAID-10 on Adaptec 51245 Emmanuel Florac
2012-06-08 19:36 ` Christian J. Dietrich
2012-06-09 13:23 ` Emmanuel Florac
2012-06-10 3:58 ` Stan Hoeppner
2012-06-08 13:56 ` Eric Sandeen
2012-06-08 19:33 ` Christian J. Dietrich
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=4FD1C9B8.70907@internet-sicherheit.de \
--to=dietrich@internet-sicherheit.de \
--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.