On Wed, Aug 12, 2020 at 04:18:37PM +0800, Chao Leng wrote: > For nvme multipath configured, just fail over to retry IO for path error, > but maybe blk_queue_dying return true, IO can not be retry at current > path, thus IO will interrupted. > > For nvme multipath configured, blk_queue_dying and path error both need > fail over to retry. We need check whether path-related errors first, and > then retry local or fail over to retry. Err, no. None of this really makes any sense. The existing code actually works perfectly well unless you really insist on trying to use a completley unsupported multipathing configuration. I would storngly recommend to not use dm-multipath with nvme, but if you insist please fix your problems without impacting the fully supported native path.
