Re: help wanted - 6-disk raid5 borked: _ _ U U U U

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

 



Neil Brown wrote:
> You shouldn't need to upgrade kernel

Ok.
I had a crazy idea that 2 devices down in a RAID5 was an MD bug.

I didn't expect MD to kick that last disk - I would have thought that
it would just pass on the read error in that situation.  If you've got
the time to explain I'd like to be wiser - why not?

> But yet, use --assemble --force and be aware that there could be data
> corruption (without knowing the history it is hard to say how
> likely).  An 'fsck' at least would be recommended.

Thanks a tera!

(Probably no corruption since I was strictly reading from the array
when the disks were kicked.)
-
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