mirror of
https://github.com/gluster/glusterd2.git
synced 2026-02-05 12:45:38 +01:00
If a Volume is cloned from another volume, the bricks of cloned volume will also belong to same LV thinpool as the original Volume. So before removing the thinpool a check was made to confirm if number of Lvs in that thinpool is zero. This check was causing hang when parallel Volume delete commands were issued. With this PR, number of Lvs check is removed, instead of that captured the failure of thinpool delete and handled it gracefully. This PR also adds support for gracefully delete the volume if lv or thinpool already deleted by previous failed transaction or manual delete. Signed-off-by: Aravinda VK <avishwan@redhat.com>