Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> writes: > Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> writes: >> NeilBrown <neilb@xxxxxxx> writes: >>> On Mon, 2 Feb 2015 07:10:14 +0000 Manibalan P <pmanibalan@xxxxxxxxxxxxxx> >>> wrote: >>> >>>> Dear All, >>>> Any updates on this issue. >>> >>> Probably the same as: >>> >>> http://marc.info/?l=linux-raid&m=142283560704091&w=2 >> >> Hi Neil, >> >> I ran some tests on this one against the latest Linus' tree as of today >> (1fa185ebcbcefdc5229c783450c9f0439a69f0c1) which I believe includes all >> your pending 3.20 patches. >> >> I am able to reproduce Manibalan's hangs on a system with 4 SSDs if I >> run fio on top of a device while it is resyncing and I fail one of the >> devices. > > Since Manibalan mentioned this issue wasn't present in earlier kernels, > I started trying to track down what change caused it. > > So far I have been able to reproduce the hang as far back as 3.10. After a lot of bisecting I finally traced the issue back to this commit: a7854487cd7128a30a7f4f5259de9f67d5efb95f is the first bad commit commit a7854487cd7128a30a7f4f5259de9f67d5efb95f Author: Alexander Lyakas <alex.bolshoy@xxxxxxxxx> Date: Thu Oct 11 13:50:12 2012 +1100 md: When RAID5 is dirty, force reconstruct-write instead of read-modify-write. Signed-off-by: Alex Lyakas <alex@xxxxxxxxxxxxxxxxx> Suggested-by: Yair Hershko <yair@xxxxxxxxxxxxxxxxx> Signed-off-by: NeilBrown <neilb@xxxxxxx> If I revert that one I cannot reproduce the hang, applying it reproduces the hang consistently. Cheers, Jes -- 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
