Hi! Now I had the time to bisect, started with 3.7 as good and 3.8 as bad. 0cfbcafcae8b7364b5fa96c2b26ccde7a3a296a9 is the bad commit. [1] block: add plug for blkdev_issue_discard
While 3.8.10 was still bad, the same kernel with the reverted patch applied is fine. I found another report. [2] Thanks, Markus [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0cfbcafcae8b7364b5fa96c2b26ccde7a3a296a9 [2] http://www.spinics.net/lists/raid/msg42758.html Markus schrieb am 24.03.2013: > Hi! > > Still the same with 3.8.4 ... anybody? > > Best regards, > Markus > > Markus schrieb am 12.03.2013: > > Hello! > > > > I created a hybrid raid1 with one ssd and one hdd. Used writemostly and > > writebehind and put ext4 with discard enabled on it. > > This setup worked quite well for the last months (last kernel was 3.7.6). > > But now as I booted 3.8.2 the hdd was dropped from the raid with: > > > md/raid1:md2: Disk failure on sdb1, disabling device. > > > md/raid1:md2: Operation continuing on 1 devices. > > > > Re-adding this drive it will try to resync but the hdd will be dropped > > short time after. Now I remounted the device without the discard flag and > > the resync and usage works as before. > > After remounting it again with discard enabled the hdd is dropped again. So > > I think this is the culprit as the hdd does obviously not support TRIM... > > > > As it worked fine before, I think this is a regression? Or is this an > > intended change? > > > > > > Thanks, > > Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
