Re: RAID 0 md device still active after pulled drive

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

 



On Friday October 17, thomas62186218@xxxxxxx wrote:
> Hi All,
> 
> I have run into a most unusual behavior, where mdadm reports a RAID 0 
> array that is missing a drive as "Active".

Not unusual at all.  mdadm has always behaved this way.

There is nothing that 'md' can ever do about a failed drive in a
raid0, so it doesn't bother doing anything.  At all.
As far as md is concerned, the drive is still an active part of the
array.  It will still try to send appropriate IO requests to that
device.  If they fail (e.g. because the device doesn't actually
exist), then md will send that error message back.
> 
> 
> Conclusion: Why does mdadm report a drive failure on RAID 0 but not 
> make the md device as Inactive or otherwise failed?

where exactly did "mdadm report a drive failure" on the RAID0 ??


As always,  if you think the documentation could be improved to reduce
the chance of this sort of confusion, or if the output of mdadm could
make something more clear, I am open to constructive suggestions (and
patches).

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