On Sun, 6 May 2018, Coly Li wrote: > On 2018/4/27 4:32 AM, Eric Wheeler wrote: > >> Hi Coly, > >> > >> I'm sure you've been busy with the v4.17 merge but I thought I > >> would check in: > >> > >> Have you had a chance to look at this? It is an opportunity to fix this > >> 4k bug for the future since we can still reproduce the error. > >> > >>>>> bcache: bch_count_io_errors() dm-6: IO error on reading from cache, recovering <<< > >> > >> What do you think, is there data corruption exposure here since 4.1.49 > >> still has the dirty-cache-recorvery bug? > > > > I just noticed that "bcache: only permit to recovery read error when cache > > device is clean" is in v4.1.49, but would this recover gracefully in the > > 4k error situation? > > > >> Also, would your failure-recovery patch series address this type of > >> failure? > > Hi Eric, > > I just find a time slot to compose a patch checking 4K alignment of I/Os > to backing device. After testing and first glance at the messages, I > will post it out. > Thank you Coly, I appreciate your help! -- Eric Wheeler > Coly Li > -- > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
