Re: Strange RAID-5 rebuild problem

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

 



Michael Guntsche wrote:

[]
Answering myself here after reading through the manapges, this seems to be a regression. Furthermore this may yield to some nasty data corruption, well at least I think it will.

* --stop the array while resyncing.
* set start_ro to 1
* Start the array, automatic reconstruction does not start even after the data is been written to the ARRAY

You can't write any data to a read-only array.

/mjt

* stop the array again
* set start_ro to 0
* Start the array again
The array picks up the resync process where it stopped the first time even if there has already been data written to it, while it was started with start_ro = 1. Won't this yield corrupted data, since data BEFORE that offset might actually have changed in the mean time?

Kind regards,
Michael

--
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