On 19.07.2019 09:43, Ruben Lozano wrote:
Hi,
I'm still trying to delete that blob when the nodes that reference it
are deleted.
Searching for delete the last reference to the blob I ended disabling
the node versioning, as I couldn't delete the node history version.
I have three cases right now:
- If I delete the node with versioning, run the version gc and the blob
gc, I ended with a frozenNode reference (protected) that avoids the blob
for being physically deleted by the blob gc.
Yes, that's expected when the version history is preserved.
- If I delete the node without versioning, avoid to run the version gc
and only run the blob gc, I ended with a reference from a logically
deleted node but the blob gc doesn't delete the blob.
Correct.
- If I create the file without versioning, run the version gc and the
blob gc, I ended with a IOException "Marked references not available",
because the blob is not being referenced anywhere.
That's not supposed to happen :-).
I thought that blob gc should delete unreferenced blobs, not throw an
exception. I'm stuck, because I don't know in what case the gc is going
to delete the blob.
Thanks for your help,
Ruben Lozano
Best regards, Julian
