[Bugs] [Bug 1568521] shard files present even after deleting vm from ovirt UI

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1568521

Vinayak Hariharmath <vharihar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vharihar at redhat.com
              Flags|                            |needinfo?(gusevmk.uni at yande
                   |                            |x.ru)



--- Comment #16 from Vinayak Hariharmath <vharihar at redhat.com> ---
Hello,
Bit of background about sharded file deletion: There are 2 parts of sharded
files 1. base file (1st shard or reference shard) 2. shards of the base file
stored as GFID.index

When we delete a sharded file
1. firstly entry of a base file created (In the name of GFID) under
.shard/.remove_me
2. next, the base file will be unlinked
3. in the background, the associated shards will be cleaned, and then finally
reference entry present at .shard/.remove_me will be removed

The reference created under .shard/.remove_me always referred to build the path
to delete the associated shards. So the background thread picks up the
".shard/remove_me" entries, builds the shards path, and deletes them. 

So with your description, It looks like steps 1 and 2 are done but the
background thread is getting ESTALE while cleaning up those .shard/.remove_me
entries, the shards left undelete and space is not freed up. 

It looks strange, why you are getting ESTALE though the entry is present at
.shard/.remove_me. Can you please post the complete logs of the time you
performed the 1st deletion? History of events also helpful to analyze the issue

Regards
Vh


-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.