Hello abhi, In a workflow for example to recreate clean env from scratch. Delete volume and create volume are used, in this order. so in term of reservation, as create volume is executed after delete,a finder executed after must return that the volume exists. Even after cache updated from dfm or ovum.
Hello Abhi, Sorry I am lost. Anil said in previous post
"There are two conflicting reservations that are happening here. One reservation thinks "test_clone" volume does not exist(REMOVE VOLUME). The other reservation thinks "test_clone" volume exists and was newly created(CREATE CLONE)." In my example we are exactly in the same conflicting situation after dfm acquire. So what I have to do to have a refresh workflow that works in all situations.