From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: failed to read root inode
Date: Sat, 08 May 2010 17:53:17 -0500 [thread overview]
Message-ID: <4BE5EB5D.5020702@hardwarefreak.com> (raw)
In-Reply-To: <4BE55A63.8070203@purplehaze.ch>
Christian Affolter put forth on 5/8/2010 7:34 AM:
> Hi
>
> After a disk crash within a hardware RAID-6 controller and kernel
> freeze, I'm unable to mount an XFS filesystem on top of an EVMS volume:
What storage management operation(s) were you performing when this crash
occurred? Were you adding, deleting, shrinking, or growing an EVMS volume
when the "crash" occurred, or was the system just sitting idle with no load
when the crash occurred?
Why did the "crash" of a single disk in a hardware RAID6 cause a kernel
freeze? What is your definition of "disk crash"? A single physical disk
failure should not have caused this under any circumstances. The RAID card
should have handled a single disk failure transparently.
Exactly which make/model is the RAID card? What is the status of each of
the remaining disks attached to the card as reported by its BIOS? What is
the status of the RAID6 volume as reported by the RAID card BIOS? What is
the status of each of your EVMS volumes as reported by the EVMS UI?
I'm asking all of these questions because it seems rather clear that the
root cause of your problem lies at a layer well below the XFS filesystem.
You have two layers of physical disk abstraction below XFS: a hardware
RAID6 and a software logical volume manager. You've apparently suffered a
storage system hardware failure, according to your description. You haven't
given any details of the current status of the hardware RAID, or of the
logical volumes, merely that XFS is having problems. I think a "Well duh!"
is in order.
Please provide _detailed_ information from the RAID card BIOS and the EVMS
UI. Even if the problem isn't XFS related I for one would be glad to assist
you in getting this fixed. Right now we don't have enough information. At
least I don't.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-08 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 12:34 failed to read root inode Christian Affolter
2010-05-08 15:06 ` Eric Sandeen
2010-05-09 14:53 ` Christian Affolter
2010-05-11 10:05 ` Christian Affolter
2010-05-08 22:53 ` Stan Hoeppner [this message]
2010-05-09 13:28 ` Emmanuel Florac
2010-05-09 14:53 ` Stan Hoeppner
2010-05-09 15:34 ` Emmanuel Florac
2010-05-10 1:09 ` Eric Sandeen
2010-05-09 15:35 ` Christian Affolter
2010-05-09 15:59 ` Emmanuel Florac
2010-05-09 17:34 ` Stan Hoeppner
2010-05-09 18:03 ` Roger Willcocks
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=4BE5EB5D.5020702@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