public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: failed to read root inode
Date: Sun, 9 May 2010 15:28:18 +0200	[thread overview]
Message-ID: <20100509152818.7481c1e1@galadriel.home> (raw)
In-Reply-To: <4BE5EB5D.5020702@hardwarefreak.com>

Le Sat, 08 May 2010 17:53:17 -0500 vous écriviez:

> 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.

The RAID array may go west if the disk isn't properly set up,
particularly if it's a desktop-class drive. 

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-05-09 13:26 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
2010-05-09 13:28   ` Emmanuel Florac [this message]
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=20100509152818.7481c1e1@galadriel.home \
    --to=eflorac@intellique.com \
    --cc=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