> I am running 2.2.12. What I don't understand is if both md0 and md1 are
> kicked out, why am I still able to use md2. I can read information
> without any problems at this point. That seems strange.
Are you sure it's not just information in the disk cache? the disk cache
can grow to be man
No, md2 is definitely mounted:
production:~# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sdg1 202182 40941150801 21% /
/dev/sdg754410 7843 43758 15% /boot
/dev/sdg6 995115 236943473 0% /h
At 08:47 PM 10/14/99 -0400, [EMAIL PROTECTED] wrote:
>I am running 2.2.12. What I don't understand is if both md0 and md1 are
>kicked out, why am I still able to use md2. I can read information
>without any problems at this point. That seems strange.
>
>Also, I'm still unclear on *which* drive
I am running 2.2.12. What I don't understand is if both md0 and md1 are
kicked out, why am I still able to use md2. I can read information
without any problems at this point. That seems strange.
Also, I'm still unclear on *which* drive specifically caused the error.
Will recreating the mirro
Jeremy wrote:
> Ok, so I know there's a bad drive in my array, but which one caused the
> errors so I can begin to replace it? Also, how do I recover without
> loosing information?
>
> Here is the info:
>
> /proc/mdstat:
> Personalities : [linear] [raid0] [raid1] [raid5] [translucent]
> read_ahea
Ok, so I know there's a bad drive in my array, but which one caused the
errors so I can begin to replace it? Also, how do I recover without
loosing information?
Here is the info:
/proc/mdstat:
Personalities : [linear] [raid0] [raid1] [raid5] [translucent]
read_ahead 1024 sectors
md2 : active r
