Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
When add leaked datapath: 1. add leaked datapath to Sr.vdis 2. write to db file 3. log enhance In XSI-1752/1753, there are storage exceptions rasied when destroying datapath. Then the procedure fails and the state of VDI becomes incorrect, which leads to various abnormal results in subsequent operations. We can find logs as "Leaked datapath: dp: xxxx". The leaked datapath is designed to redestory the datapath and refresh the state before next storage operation via function remove_datapaths_andthen_nolock. But we don't find logs about redestorying like "Attempting to destroy datapath". It seems leaked datapath mechanism doesn't take effect. This commit is to fix this bug. We should add leaked datapath to Sr.vdis to make the leaked datapath realy work. And write to db file to avoid losing the leaked datapath when xapi restart. Signed-off-by: Changlei Li <[email protected]>
- Loading branch information