[Bugs] [Bug 1811631] brick crashed when creating and deleting volumes over time (with brick mux enabled only)

[bugzilla at redhat.com]

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



--- Comment #1 from Mohit Agrawal <moagrawa at redhat.com> ---
In brick_mux environment, while volumes are created/stopped in a loop after
running a long time the main brick is crashed.
Brick is crashed because the main brick process was not cleaned up memory for
all objects at the time of detaching a volume.
Below are the objects that are missed at the time of detaching a volume
1) xlator object for a brick graph
2) local_pool for posix_lock xlator
3) rpc object cleanup at quota xlator
4) inode leak at brick xlator

To avoid the leak needs to clean up all objects at the time of detaching a
brick.

Reproducer:
1.created 3 node setup, brickmux enabled
2.created 2 volumes, one called base_x3 of type x3, and another of type arbiter
named "basevol_bitter"
the above 2 volumes will not be deleted at all throughout the test
3.now started creating volumes, starting them in batches of 100, and then
delete them
4. the above step#3 was to go on for a few days

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