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, [EMAIL PROTECTED] 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
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
