From: Guido Moonen <guido.moonen@axon.tv>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 - 4 disk reboot trouble.
Date: Thu, 11 May 2006 14:00:09 +0200 [thread overview]
Message-ID: <44632749.7010600@axon.tv> (raw)
In-Reply-To: <17507.9569.225607.513520@cse.unsw.edu.au>
Hi,
Computers in the field will be able to complete the whole cycle of
recovering and having a redundent array. but this is a situation that
can happen, and we are not sure what is causing this problem. I will let
one complete the this recovery and try to reproduce this bug. But when a
customer will replace one the drives this process is started again and
there will be a period where the system is not full proof.
System use:
This system will record (24/7) a single channel and saves the recorded
data (MPEG) on a raid device. The system must be able to hold 90 days of
recorded material for compliance regulation. When the raid fails users
can lose upto 90 days of mpeg which is not acceptable for compliance
(They must be able to produce the recorded mpeg for 90 days). So we
would like to know if this failure can be avoided, or if there is
another configuration which makes it possible to recover from this state.
Guido.
Neil Brown wrote:
>On Thursday May 11, guido.moonen@axon.tv wrote:
>
>
>>Hi,
>>
>>I'm running a raid5 system, and when I reboot my raid seems to be
>>failing. (One disk is set to spare and other disk seems to be oke in the
>>detials page but we get a INPUT/OUTPUT error when trying to mount it)
>>
>>We cannot seem te find the problem in this setup.
>>
>>
>...
>
>
>> State : clean, degraded, recovering
>>
>>
> ^^^^^^^^^^
>
>Do you ever let the recovery actually finish? Until you do you don't
>have real redundancy.
>
>NeilBrown
>
>
>
next prev parent reply other threads:[~2006-05-11 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 11:46 RAID5 - 4 disk reboot trouble Guido Moonen
2006-05-11 11:52 ` Neil Brown
2006-05-11 12:00 ` Guido Moonen [this message]
2006-05-11 14:15 ` Guido Moonen
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=44632749.7010600@axon.tv \
--to=guido.moonen@axon.tv \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).