Commit dc651b3
committed
CA-402901: Update leaked dp to Sr
When add leaked datapath:
1. add leaked datapath to Sr.vdis
2. write to db file
3. log enhance
If there are storage exceptions raised when destroying datapath,
the procedure fails and the state of VDI becomes incorrect,
which leads to various abnormalresults in subsequent operations.
To handle this, the leaked datapath is designed to redestroy the
datapath and refresh the state before next storage operation via
function remove_datapaths_andthen_nolock. But this mechanism
doesn't take effect in current code.
This commit is to fix this bug. leaked datapath should be added
to Sr.vdis to make the leaked datapath really work. And write to
db file to avoid losing the leaked datapath if xapi restarts.
Signed-off-by: Changlei Li <[email protected]>1 parent 27e4e25 commit dc651b3
1 file changed
+15
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
459 | 459 | | |
460 | 460 | | |
461 | 461 | | |
| 462 | + | |
| 463 | + | |
| 464 | + | |
| 465 | + | |
462 | 466 | | |
463 | 467 | | |
464 | 468 | | |
| |||
479 | 483 | | |
480 | 484 | | |
481 | 485 | | |
| 486 | + | |
| 487 | + | |
| 488 | + | |
| 489 | + | |
| 490 | + | |
| 491 | + | |
| 492 | + | |
| 493 | + | |
| 494 | + | |
482 | 495 | | |
483 | 496 | | |
484 | 497 | | |
| |||
535 | 548 | | |
536 | 549 | | |
537 | 550 | | |
538 | | - | |
| 551 | + | |
| 552 | + | |
539 | 553 | | |
540 | 554 | | |
541 | 555 | | |
| |||
0 commit comments