> Leen de Braal wrote:
>> When checking /proc/mdstat I see this:
>>
>> linux:~ # cat /proc/mdstat
>> Personalities : [raid1]
>> md0 : active raid1 hdb3[1]
>>       155219904 blocks [2/1] [_U]
>>
>> unused devices: <none>
>> linux:~ #
>>
> I would suggest using mdadm --detail /dev/md0 I think the output is a
> bit clearer.
>> Could someone help me interpret what is shown here?
>>
> from looking at mine, it reads it is an active raid1 array running only
> on hdb3, which is the second device in the array (first is 0).  Summary
> it is a 2 disk raid running on 1 disk, first disk is missing.
>> As I see it, one drive is missing from the raid-array, but then it says:
>> unused devices: none.
>> It is /dev/hda3 and /dev/hdb3 that were initially setup as raid1.
>>
> mdadm --detail /dev/md0 will tell you more.

    Update Time : Tue Mar  6 13:22:40 2007
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : aed4ffaa:f90aa9b6:be5af158:c22c8924
         Events : 0.9596839

    Number   Major   Minor   RaidDevice State
       0       0        0        -      removed
       1       3       67        1      active sync   /dev/hdb3
linux:~ #

>> And if hda3 is missing, can I add it back to a live and running system?
>>
> Yes.  mdadm /dev/md0 -a /dev/hda3
>> What happens when I add it and the drive is broken?
>>
> It will tell you.  again, use mdadm --detail /dev/md0 for info on what
> is happening to your array.

linux:~ # mdadm /dev/md0 -a /dev/hda3
mdadm: hot added /dev/hda3
linux:~ # cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hda3[2] hdb3[1]
      155219904 blocks [2/1] [_U]
      [>....................]  recovery =  0.0% (150208/155219904)
finish=120.3min speed=21458K/sec

unused devices: <none>
linux:~ #


It seems, that resyncing is going on now.

    Update Time : Tue Mar  6 13:26:30 2007
          State : clean, degraded, recovering
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

 Rebuild Status : 3% complete

           UUID : aed4ffaa:f90aa9b6:be5af158:c22c8924
         Events : 0.9596970

    Number   Major   Minor   RaidDevice State
       0       0        0        -      removed
       1       3       67        1      active sync   /dev/hdb3

       2       3        3        0      spare rebuilding   /dev/hda3
linux:~ #


Still asking myself how this could have happened? Any idea?

>
>
-- 
L. de Braal
BraHa Systems
NL - Terneuzen
T +31 115 649333
F +31 115 649444
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to