Re: 'Array state: ... 1 failed', but array clean?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 28 Jan 2010 13:59:39 +0100
Michał Sawicz <michal@xxxxxxxxxx> wrote:

> Dnia 2010-01-28, czw o godzinie 13:09 +0100, Michał Sawicz pisze:
> > Where does this 'failed' come from? Oh, and it's like that on all
> > members. Is my array safe as /proc/mdstat says? 
> 
> Hmm I think it might be related to this:
> 
> > # mdadm -E /dev/sdb1
> > [...]
> >     Array Slot : 6 (0, failed, 2, 3, 1, 5, 4)
> >    Array State : uuuuUu 1 failed
> 
> One of the disks in this array was swapped, maybe this is what this info
> records? How can I get rid of that?
> 

The device that was the second device added to the array failed (or
disappeared), and this fact is recorded in case that device ever reappears...

Yes, this is confusing.  mdadm-3.x report the array state differently.

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux